Triple
T16036818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arrondissement of Péronne |
E388988
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Moreuil |
E797045
|
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: Moreuil | Statement: [arrondissement of Péronne, contains, Moreuil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moreuil Context triple: [arrondissement of Péronne, contains, Moreuil]
-
A.
Moreuil
chosen
Moreuil is a small commune in northern France, located in the Somme department in the Hauts-de-France region.
-
B.
Chamrousse
Chamrousse is a French alpine ski resort and mountain commune in the Alps, known for its winter sports facilities and scenic high-altitude landscapes.
-
C.
Villeroux
Villeroux is a small village in the municipality of Vaux-sur-Sûre in the Walloon region of Belgium.
-
D.
Olbreuse
Olbreuse is a small locality in western France historically notable as the ancestral seat of the noble d’Olbreuse family.
-
E.
Gressoney
Gressoney is a mountain community in the Italian Alps known as a key center of Walser culture, language, and traditions.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1833ca66881909475fac23e6fbf86 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff796fafc8190b6cfb2d8ea502eef |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 4:56 a.m.