Triple
T14055577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Star Flyer |
E338210
|
entity |
| Predicate | hasRiderSeating |
P2608
|
FINISHED |
| Object | swing chairs |
—
|
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: swing chairs | Statement: [The Star Flyer, hasRiderSeating, swing chairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiderSeating Context triple: [The Star Flyer, hasRiderSeating, swing chairs]
-
A.
hasSeating
chosen
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
B.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
C.
hasLongitudinalSeating
Indicates that an entity features seating arranged lengthwise along its sides rather than across its width.
-
D.
hasBermSeating
Indicates that a venue or location includes berm-style seating areas, typically grass-covered embankments where spectators can sit.
-
E.
hasRetractableSeating
Indicates that an entity is equipped with seating that can be folded away, collapsed, or otherwise retracted when not in use.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8d1aa48190a5055d15d9fa220c |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.