Triple
T35649112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 823 |
E1030091
|
entity |
| Predicate | precededByRoute |
P118481
|
FINISHED |
| Object | SR 821 |
—
|
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: SR 821 | Statement: [SR 823, precededByRoute, SR 821]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByRoute Context triple: [SR 823, precededByRoute, SR 821]
-
A.
isPrecededOnRouteBy
chosen
Indicates that one element on a route comes immediately before another in the ordered sequence of that route.
-
B.
precededBySegment
Indicates that one segment occurs immediately before another segment in a sequence or ordering.
-
C.
precededByInPosition
Indicates that one entity occurs or appears immediately before another entity in a specific ordered position or sequence.
-
D.
precededByArc
Indicates that one element or event occurs immediately before another along a directed arc or ordered sequence.
-
E.
precededByInProtocol
Indicates that one step, action, or element in a protocol occurs earlier in the defined sequence than another, directly preceding it in order.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 3, 2026, 4:05 p.m.