Triple
T14724534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peine |
E345903
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Fuhse |
E171019
|
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: Fuhse | Statement: [Peine, locatedOnRiver, Fuhse]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fuhse Context triple: [Peine, locatedOnRiver, Fuhse]
-
A.
Fuhse
chosen
Fuhse is a river in Lower Saxony, Germany, that flows through several towns before joining the Aller River.
-
B.
Fuhne
The Fuhne is a river in the German state of Saxony-Anhalt that flows through the Anhalt-Bitterfeld district before joining the Saale.
-
C.
Fuchs
Fuchs is a German surname borne by numerous notable individuals across fields such as science, politics, and the arts.
-
D.
Fogarasch
Fogarasch is a historic Transylvanian town, today known as Făgăraș in central Romania, noted for its medieval fortress and role in the region’s Saxon and Romanian history.
-
E.
Fuscherkarkopf
Fuscherkarkopf is a prominent alpine peak in the Austrian Alps, known for its high elevation and location within the Glockner Group of the Hohe Tauern range.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec25e9a14819081fa06fc601f295d |
completed | April 14, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf09791e081908a1262717fd31445 |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 10, 2026, 1:29 a.m.