Triple
T11133303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unstrut |
E263342
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Artern |
E671296
|
NE 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: Artern | Statement: [Unstrut, flowsThrough, Artern]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Artern Context triple: [Unstrut, flowsThrough, Artern]
-
A.
Artern
chosen
Artern is a small town in the German state of Thuringia, known for its location along the Unstrut River and its historical salt production.
-
B.
Arvit
Arvit is the Jewish evening prayer service recited daily after nightfall.
-
C.
Attert
Attert is a small municipality and town in the Walloon region of Belgium, near the border with Luxembourg, known for its rural character and cross-border community ties.
-
D.
Arth
Arth is a Swiss lakeside municipality in the canton of Schwyz, situated on the shores of Lake Zug and known for its scenic Alpine surroundings.
-
E.
Arrott
Arrott is the station code for the Arrott Transportation Center, a public transit hub in Philadelphia, Pennsylvania.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8347a248190837e8c26f25f553a |
completed | April 9, 2026, 5:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e441f00d7c8190a8fe8e0c1169e6b0 |
completed | April 19, 2026, 2:46 a.m. |
Created at: April 8, 2026, 9:28 p.m.