Triple
T14163480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyderabad International Convention Centre |
E351007
|
entity |
| Predicate | hasBanquetCapacity |
P113070
|
FINISHED |
| Object | 2500 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2500 | Statement: [Hyderabad International Convention Centre, hasBanquetCapacity, 2500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBanquetCapacity Context triple: [Hyderabad International Convention Centre, hasBanquetCapacity, 2500]
-
A.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
standingCapacity
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
-
C.
typicalSeatingCapacityUpperBound
Indicates the maximum number of seats that a venue or vehicle is typically designed or allowed to accommodate under normal conditions.
-
D.
roomCapacity
Indicates the maximum number of people or occupants that a room is designed or allowed to hold.
-
E.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de613a4a2081908fd51bf4b4d82b6c |
completed | April 14, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:59 a.m.