Triple
T6046364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giengen an der Brenz |
E134675
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Brenz |
E111222
|
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: Brenz | Statement: [Giengen an der Brenz, locatedOnRiver, Brenz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brenz Context triple: [Giengen an der Brenz, locatedOnRiver, Brenz]
-
A.
Brenz
chosen
The Brenz is a river in southern Germany that flows through Baden-Württemberg and Bavaria before joining the Danube.
-
B.
Brenner
Brenner is a surname of German origin borne by various notable individuals across fields such as science, politics, and the arts.
-
C.
Breng
Breng is a Dutch public transport operator providing regional bus and train services in and around Arnhem and Nijmegen in the Netherlands.
-
D.
Brennen
Brennen is a given name, typically used as a variant spelling of Brennan.
-
E.
Brupass
Brupass is an integrated public transport ticketing system that allows seamless travel across multiple operators and modes within the Brussels metropolitan area.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e53f508190864be04bc016c525 |
completed | March 22, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c113a2b65c8190a1891e790cb9a5de |
completed | March 23, 2026, 10:19 a.m. |
Created at: March 22, 2026, 4:09 p.m.