Triple
T4535333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajoie |
E107394
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Boncourt |
E56934
|
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: Boncourt | Statement: [Ajoie, contains, Boncourt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boncourt Context triple: [Ajoie, contains, Boncourt]
-
A.
Boncourt
chosen
Boncourt is a locality known for its historic Château de Boncourt, reflecting its cultural and architectural heritage.
-
B.
Couvet
Couvet is a village in the Val-de-Travers district of the canton of Neuchâtel in western Switzerland, known historically as the birthplace of the jurist Emer de Vattel.
-
C.
Ducos
Ducos is a French surname most notably borne by Pierre-Roger Ducos, a political figure during the French Revolution and the Consulate.
-
D.
Boulzane
Boulzane is a river in southern France that serves as a tributary of the Agly.
-
E.
Boussy-Saint-Antoine
Boussy-Saint-Antoine is a suburban commune in the Essonne department in the Île-de-France region of northern France.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57b634b08190845d04213cf8d5b9 |
completed | March 20, 2026, 2:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdb9193e2481908901b9b4eb307da8 |
completed | March 20, 2026, 9:16 p.m. |
Created at: March 20, 2026, 1:04 p.m.