Triple
T24892730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annappes |
E623046
|
entity |
| Predicate | formerAdministrativeClassification |
P120323
|
FINISHED |
| Object | commune of Nord |
—
|
LITERAL 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: commune of Nord | Statement: [Annappes, formerAdministrativeClassification, commune of Nord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAdministrativeClassification Context triple: [Annappes, formerAdministrativeClassification, commune of Nord]
-
A.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
formerCategory
Indicates that an entity previously belonged to a given category but no longer does.
-
C.
wasFormerlyClassifiedAs
chosen
Indicates that an entity previously belonged to a particular class or category but no longer does so.
-
D.
formerAdministeredBy
Indicates that an entity was previously administered or managed by another entity, but is no longer under that administration.
-
E.
previousClassification
Indicates that one classification precedes another in time or in an ordered sequence of classifications.
- F. None of above.
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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 5:26 a.m.