Triple
T26590487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rommen station |
E667338
|
entity |
| Predicate | followedByStationOnLine |
P42146
|
FINISHED |
| Object | Stovner station |
—
|
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: Stovner station | Statement: [Rommen station, followedByStationOnLine, Stovner station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByStationOnLine Context triple: [Rommen station, followedByStationOnLine, Stovner station]
-
A.
followedByStationOnLineM2
Indicates that one station is immediately followed by another station along metro line M2 in the direction of travel.
-
B.
followedByStationOnLine1
Indicates that one station directly succeeds another station along the sequence of stops on Line 1.
-
C.
followedByStation
chosen
Indicates that one station directly succeeds another in a sequence, such as along a transit line or route.
-
D.
followingStationOnYellowLine
Indicates that one station is the next station in sequence after another on the Yellow Line.
-
E.
hasAdjacentStationOnLine 5
Indicates that one station is directly next to another station along line 5, with no other stations in between on that line.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 2:07 a.m.