Triple
T1024733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osnabrück |
E22113
|
entity |
| Predicate | twinCity |
P1072
|
FINISHED |
| Object | Angers |
E71733
|
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: Angers | Statement: [Osnabrück, twinCity, Angers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Angers Context triple: [Osnabrück, twinCity, Angers]
-
A.
Angers
chosen
Angers is a historic city in western France known for its medieval architecture, including the Château d'Angers and its famous Apocalypse Tapestry.
-
B.
Mâcon
Mâcon is a historic town in eastern France’s Burgundy region, known for its wine production and picturesque setting along the Saône River.
-
C.
Poitiers
Poitiers is a historic city in western France known for its Romanesque architecture, medieval heritage, and role as a regional center in the Nouvelle-Aquitaine region.
-
D.
Nantes
Nantes is a historic port city in western France on the Loire River, known for its maritime heritage, cultural institutions, and vibrant arts scene.
-
E.
Amiens
Amiens is a historic city in northern France, known for its Gothic cathedral and role as the site of the 1802 Treaty of Amiens.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7e28df08190b5be7794442a6f21 |
completed | March 1, 2026, 10:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ada9536bec8190acf50065863bd16a |
completed | March 8, 2026, 4:52 p.m. |
Created at: March 1, 2026, 7:41 p.m.