Triple
T6705795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacoma Dome |
E153000
|
entity |
| Predicate | hasRetractableSeating |
P72541
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tacoma Dome, hasRetractableSeating, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetractableSeating Context triple: [Tacoma Dome, hasRetractableSeating, yes]
-
A.
hasRetractablePitch
Indicates that an entity (typically a stadium or venue) possesses a playing surface or pitch that can be mechanically extended or withdrawn as needed.
-
B.
seatRecline
Indicates that one entity adjusts or is capable of adjusting the backward tilt or reclining position of a seat relative to another entity or context.
-
C.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
D.
seatFeature
Indicates that a seat possesses or is equipped with a particular feature or characteristic.
-
E.
hasLongitudinalSeating
Indicates that an entity features seating arranged lengthwise along its sides rather than across its width.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:06 p.m.