Triple
T17117714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canton of Annecy-le-Vieux |
E415382
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Pringy |
E1235451
|
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: Pringy | Statement: [Canton of Annecy-le-Vieux, contains, Pringy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pringy Context triple: [Canton of Annecy-le-Vieux, contains, Pringy]
-
A.
Pringy
chosen
Pringy is a commune in southeastern France that forms part of the urban area around the city of Annecy in the Haute-Savoie department.
-
B.
Pringi
Pringi is a small coastal village in northern Estonia, located within Viimsi Parish near the capital city of Tallinn.
-
C.
Pervyse
Pervyse is a village in West Flanders, Belgium, known for its location on the World War I Yser Front and the heavy fighting that took place there.
-
D.
Priller
Priller is a German surname most notably associated with Josef Priller, a famous Luftwaffe fighter ace of World War II.
-
E.
Prye
Prye is an alternative transliteration of Pyay, a historic city in central Myanmar located on the Irrawaddy River.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e8075a6c8190954d36eb94d1028a |
completed | April 18, 2026, 8:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a013a0b69108190ba3ba6ba7f8d3935 |
completed | May 11, 2026, 2:08 a.m. |
Created at: April 10, 2026, 5:35 a.m.