Triple
T28944797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N5 national route |
E730549
|
entity |
| Predicate | startDirectionFromWinburg |
P196075
|
FINISHED |
| Object | east |
—
|
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: east | Statement: [N5 national route, startDirectionFromWinburg, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDirectionFromWinburg Context triple: [N5 national route, startDirectionFromWinburg, east]
-
A.
directionFromBerlin
Indicates the cardinal or relative compass direction in which one entity is located when viewed from Berlin.
-
B.
directionFromBucharest
Indicates the cardinal or relative direction in which one entity lies when measured from Bucharest.
-
C.
directionFromBern
Indicates the cardinal or relative direction in which one entity is located when measured outward starting from Bern.
-
D.
roadDirectionFromNorseman
Indicates the direction or path that a road takes when starting from Norseman.
-
E.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
- F. None of above. chosen
Provenance (4 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 28, 2026, 8:39 a.m.