Triple
T38132155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i360 observation tower |
E952251
|
entity |
| Predicate | podCapacity |
P80385
|
FINISHED |
| Object | up to 200 people |
—
|
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: up to 200 people | Statement: [i360 observation tower, podCapacity, up to 200 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: podCapacity Context triple: [i360 observation tower, podCapacity, up to 200 people]
-
A.
unitCapacity
chosen
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
B.
playerCapacity
Indicates the maximum number of players that can simultaneously participate in or be accommodated by something (such as a game, session, or venue).
-
C.
sleepingCapacity
Indicates the maximum number of people or occupants that can sleep in or be accommodated for sleeping by something.
-
D.
roomCapacity
Indicates the maximum number of people or occupants that a room is designed or allowed to hold.
-
E.
stageCapacity
Indicates the maximum number of people or amount of occupancy that a particular stage can accommodate.
- F. None of above.
Provenance (3 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.