Triple
T25884748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRYJ |
E652155
|
entity |
| Predicate | previousStationCodeFor |
P75590
|
FINISHED |
| Object | Allahabad Junction |
—
|
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: Allahabad Junction | Statement: [PRYJ, previousStationCodeFor, Allahabad Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStationCodeFor Context triple: [PRYJ, previousStationCodeFor, Allahabad Junction]
-
A.
formerStationCode
chosen
Indicates that an entity previously had a specific station code that is no longer in current use.
-
B.
precedingStation
Indicates that one station is located immediately before another station in a route or sequence.
-
C.
precedingStationTowards
Indicates that one station is immediately before another station along a specified direction or route toward a given destination.
-
D.
previousStationOnLine1
Indicates that one station is the immediately preceding station to another station along transit line 1.
-
E.
precedingStationOnLine2
Indicates that one station is immediately before another station along the sequence of stops on transit line 2.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 22, 2026, 8:17 a.m.