Triple
T27813482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Rock Union Station |
E702596
|
entity |
| Predicate | servedFormerlyBy |
P19592
|
FINISHED |
| Object | Missouri Pacific Railroad |
—
|
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: Missouri Pacific Railroad | Statement: [Little Rock Union Station, servedFormerlyBy, Missouri Pacific Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedFormerlyBy Context triple: [Little Rock Union Station, servedFormerlyBy, Missouri Pacific Railroad]
-
A.
historicallyServedBy
chosen
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
B.
originallyServes
Indicates that an entity was initially intended or designated to serve, function for, or be used by another entity or purpose.
-
C.
servedBefore
Indicates that one entity was served prior to another in time or sequence.
-
D.
laterServedBy
Indicates that one entity is subsequently served or provided service by another entity at a later time.
-
E.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 27, 2026, 5:44 p.m.