Triple
T27179602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Høyenhall station |
E683153
|
entity |
| Predicate | originalSystem |
P147859
|
FINISHED |
| Object | Oslo Tramway suburban line |
—
|
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: Oslo Tramway suburban line | Statement: [Høyenhall station, originalSystem, Oslo Tramway suburban line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSystem Context triple: [Høyenhall station, originalSystem, Oslo Tramway suburban line]
-
A.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
B.
previousSystemName
Indicates that an entity was formerly known by a different system name prior to its current designation.
-
C.
startingSystem
Indicates the system or context from which an action, process, or transition is initially begun.
-
D.
previouslyUsedSystem
chosen
Indicates that an entity made use of a particular system at some time in the past, prior to the current context or state.
-
E.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 27, 2026, 9:27 a.m.