Triple
T15180950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lantosque |
E362740
|
entity |
| Predicate | hasDemonym |
P191
|
FINISHED |
| Object | Lantosquois |
E362740
|
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: Lantosquois | Statement: [Lantosque, hasDemonym, Lantosquois]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lantosquois Context triple: [Lantosque, hasDemonym, Lantosquois]
-
A.
Lantosque
chosen
Lantosque is a small picturesque commune in southeastern France, nestled in the Vésubie Valley of the Alpes-Maritimes department in the Provence-Alpes-Côte d'Azur region.
-
B.
Levasy
Levasy is a small city located in Jackson County in the U.S. state of Missouri.
-
C.
Heustreu
Heustreu is a small municipality in the Rhön-Grabfeld district of northern Bavaria, Germany, known for its rural character and location near the Rhön Mountains.
-
D.
Plerguer
Plerguer is a small commune in the Ille-et-Vilaine department of Brittany in northwestern France.
-
E.
Raguil
Raguil is an alternative spelling of Raguel, a traditional archangel name found in various Judeo-Christian angelologies.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00664caac81909bee1268264769f8 |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec89210e081909e8077fa2487c40e |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 10, 2026, 3:09 a.m.