Triple
T14005904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Tecklenburg |
E336945
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Tecklenburg |
E965942
|
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: Tecklenburg | Statement: [County of Tecklenburg, namedAfter, Tecklenburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tecklenburg Context triple: [County of Tecklenburg, namedAfter, Tecklenburg]
-
A.
Tecklenburg
chosen
Tecklenburg is a historic small town in North Rhine-Westphalia, Germany, known for its medieval architecture and open-air theater.
-
B.
Ebermannstadt
Ebermannstadt is a small historic town in northern Bavaria, Germany, known as a gateway to the scenic Franconian Switzerland region.
-
C.
Gevelsberg
Gevelsberg is a town in North Rhine-Westphalia, Germany, situated in the Ennepe-Ruhr district within the Ruhr metropolitan region.
-
D.
Diemelstadt
Diemelstadt is a small town in the German state of North Rhine-Westphalia, known for its rural character and location near the Diemel River.
-
E.
Fritzlar
Fritzlar is a historic town in northern Hesse, Germany, known for its well-preserved medieval old town and its significance in early German Christian history.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed327d88190a53af5768468a8eb |
completed | April 14, 2026, 12:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff82dcec0c8190a5e4ac0aafd34504 |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 9, 2026, 10:19 p.m.