Triple
T13493429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chambois |
E320695
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Trun |
E258341
|
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: Trun | Statement: [Chambois, locatedNear, Trun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Trun Context triple: [Chambois, locatedNear, Trun]
-
A.
Trun
chosen
Trun is a commune in northwestern France that became historically significant as a focal point in the closing encirclement of German forces during the Battle of the Falaise Pocket in World War II.
-
B.
Trun
Trun is a municipality in the Surselva Region of the canton of Graubünden in eastern Switzerland.
-
C.
Trasmondo
Trasmondo is an Italian given name historically associated with the noble Conti di Segni family.
-
D.
Troizen
Troizen is an ancient town in the northeastern Peloponnese of Greece, traditionally associated with the myths of Theseus and located within the region of Argolid.
-
E.
Kamorta
Kamorta is a significant inhabited island and settlement in India’s Nicobar archipelago, known for its strategic location and indigenous Nicobarese communities.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4c66008190b287e0551889d7c8 |
completed | April 12, 2026, 2:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7463d3a948190aab07a25fd903d4e |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:43 p.m.