Triple
T25942545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oslo Tramway line 19 |
E653744
|
entity |
| Predicate | serviceAreaDirection |
P13415
|
FINISHED |
| Object | southeastern Oslo |
—
|
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: southeastern Oslo | Statement: [Oslo Tramway line 19, serviceAreaDirection, southeastern Oslo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAreaDirection Context triple: [Oslo Tramway line 19, serviceAreaDirection, southeastern Oslo]
-
A.
serviceDirection
chosen
Indicates the direction or orientation in which a service is provided or operates relative to involved entities.
-
B.
servesDirection
Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
-
C.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
-
D.
serviceAreaName
Indicates the designated name of the geographic or functional area that a service covers or operates within.
-
E.
servedByDirection
Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 22, 2026, 8:41 a.m.