Triple
T30686287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma City–Fort Worth |
E781193
|
entity |
| Predicate | connectsWithRailServiceAtFortWorth |
P71547
|
FINISHED |
| Object | Amtrak Texas Eagle |
—
|
NE NERFINISHED |
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: Amtrak Texas Eagle | Statement: [Oklahoma City–Fort Worth, connectsWithRailServiceAtFortWorth, Amtrak Texas Eagle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsWithRailServiceAtFortWorth Context triple: [Oklahoma City–Fort Worth, connectsWithRailServiceAtFortWorth, Amtrak Texas Eagle]
-
A.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
B.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
C.
hasPassengerRailConnection
chosen
Indicates that there exists a passenger rail service linking one location or transport node to another.
-
D.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
E.
hasAdjacentRailService
Indicates that one location has rail service situated directly next to or immediately bordering it.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 29, 2026, 8:33 p.m.