Triple
T20358727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak long-distance routes |
E496718
|
entity |
| Predicate | includeAccommodationType |
P122955
|
FINISHED |
| Object | coach seating |
—
|
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: coach seating | Statement: [Amtrak long-distance routes, includeAccommodationType, coach seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeAccommodationType Context triple: [Amtrak long-distance routes, includeAccommodationType, coach seating]
-
A.
accommodationStyle
Indicates the manner or type of lodging or housing arrangement provided or used in a given context.
-
B.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
C.
passengerAccommodation
chosen
Indicates that an entity provides or is designated as seating, lodging, or space intended for use by passengers.
-
D.
sleepingAccommodation
Indicates that one entity serves as a place or facility where another entity can sleep or stay overnight.
-
E.
includesResortType
Indicates that one entity contains or offers a specific type or category of resort as part of its overall composition or services.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678573fc481908bf257e6ed41d750 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.