Triple
T5468624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanford station |
E122774
|
entity |
| Predicate | primaryModeServed |
P1302
|
FINISHED |
| Object | intercity rail |
—
|
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: intercity rail | Statement: [Sanford station, primaryModeServed, intercity rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryModeServed Context triple: [Sanford station, primaryModeServed, intercity rail]
-
A.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
B.
primaryMode
chosen
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
C.
primaryVariantInService
Indicates that a particular variant is the main or default version currently active or in use within a given service or system.
-
D.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
E.
servesMode
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.