Triple
T20358733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak long-distance routes |
E496718
|
entity |
| Predicate | includeService |
P132992
|
FINISHED |
| Object | dining car service |
—
|
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: dining car service | Statement: [Amtrak long-distance routes, includeService, dining car service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeService Context triple: [Amtrak long-distance routes, includeService, dining car service]
-
A.
includesServiceFrom
chosen
Indicates that one entity’s offering or package contains, incorporates, or makes use of a service provided by another entity.
-
B.
includesServiceFor
Indicates that one entity’s offering or package contains or covers a particular service provided for another entity.
-
C.
integratesService
Indicates that one entity connects with and enables the functionality of another service so they work together as a unified system.
-
D.
includesServicePattern
Indicates that one entity contains or incorporates a particular service pattern as part of its structure or configuration.
-
E.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
- 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.