Triple
T12026183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont de Recouvrance |
E286282
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Tour Tanguy |
E286284
|
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: Tour Tanguy | Statement: [Pont de Recouvrance, locatedNear, Tour Tanguy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tour Tanguy Context triple: [Pont de Recouvrance, locatedNear, Tour Tanguy]
-
A.
Tour Tanguy
chosen
Tour Tanguy is a medieval tower in Brest, France, now serving as a local history museum showcasing the city’s past.
-
B.
Tournier
Tournier is a surname of French origin, sometimes used as a variant of the English surname Turner.
-
C.
Tanguy
Tanguy is a French surname most notably associated with Yves Tanguy, a prominent 20th-century Surrealist painter.
-
D.
Rol-Tanguy
Rol-Tanguy was a prominent French Resistance leader during World War II, best known for his role in organizing and leading the liberation of Paris in 1944.
-
E.
Chaloub
Chaloub is a surname of likely Arabic origin, used as a transliteration variant of the name Chalhub.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903f02638819091e0cc0e93fa5ea7 |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48b8111b88190a42a8904a2d26862 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 8, 2026, 9:47 p.m.