Triple
T22095414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arrondissement of Compiègne |
E546013
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Compiègne |
—
|
NE NERFINISHED |
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: Compiègne | Statement: [arrondissement of Compiègne, capital, Compiègne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Compiègne Context triple: [arrondissement of Compiègne, capital, Compiègne]
-
A.
Compiegne
chosen
Compiègne is a historic city in northern France known for its royal château, forest, and role in significant events such as the signing of the 1918 Armistice.
-
B.
Creil
Creil is a village in the Dutch province of Flevoland, located in the reclaimed polder landscape of the Noordoostpolder.
-
C.
Creil
Creil is a commuter town in northern France’s Oise department, known as a regional rail hub connecting Paris with Picardy via major train and RER lines.
-
D.
Reims
Reims is a historic city in northeastern France known for its Gothic cathedral, role in French coronations, and significance during both World Wars.
-
E.
Lubersac
Lubersac is a small commune in the Corrèze department of south-central France, known for its rural character and traditional Limousin heritage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e82c1481908701f255b834f192 |
completed | April 28, 2026, 9:38 p.m. |
Created at: April 16, 2026, 8:29 p.m.