Triple
T11887268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soisy-sous-Montmorency |
E282818
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Andenne |
E715885
|
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: Andenne | Statement: [Soisy-sous-Montmorency, hasTwinTown, Andenne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Andenne Context triple: [Soisy-sous-Montmorency, hasTwinTown, Andenne]
-
A.
Andenne
chosen
Andenne is a municipality and town in Wallonia, Belgium, situated along the Meuse River in the province of Namur.
-
B.
Anleifr
Anleifr is a Norse personal name, likely referring to a historical or legendary Scandinavian figure associated with individuals named Óláfr in medieval sources.
-
C.
Audenarde
Audenarde (Oudenaarde) is a historic city in East Flanders, Belgium, known for its medieval architecture, tapestry production, and role in early modern European conflicts.
-
D.
Essenrode
Essenrode is a small village in Lower Saxony, Germany, historically associated with the noble von Hardenberg family.
-
E.
Felindre
Felindre is a small rural village in Wales situated within the City and County of Swansea, known for its scenic surroundings and traditional community character.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a13370819086386fecb99e4f0b |
completed | April 10, 2026, 10:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f417da310c8190aa04df2a316a5dd0 |
completed | May 1, 2026, 3:02 a.m. |
Created at: April 8, 2026, 9:44 p.m.