Triple
T21746145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R533 road |
E536792
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Ohrigstad |
—
|
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: Ohrigstad | Statement: [R533 road, terminus, Ohrigstad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ohrigstad Context triple: [R533 road, terminus, Ohrigstad]
-
A.
Ohrigstad
chosen
Ohrigstad is a small rural town in South Africa’s Mpumalanga province, known as a gateway to the Panorama Route and nearby natural attractions such as the Blyde River Canyon.
-
B.
Svarstad
Svarstad is a Norwegian surname associated with individuals such as Maren Svarstad.
-
C.
Steenodde
Steenodde is a small coastal village on the North Sea island of Amrum in Germany, known for its tranquil atmosphere and maritime surroundings.
-
D.
Stordal
Stordal is a small village and former municipality in western Norway, known for its scenic fjord landscape and traditional Norwegian architecture.
-
E.
Gangstad
Gangstad is a small settlement located within the municipality of Inderøy in Trøndelag county, Norway.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a76540c8190b91a67f4a70869fb |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 16, 2026, 6:49 p.m.