Triple
T30817533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil départemental (France) |
E784824
|
entity |
| Predicate | previousMemberTitle |
P60448
|
FINISHED |
| Object | conseillers généraux |
—
|
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: conseillers généraux | Statement: [Conseil départemental (France), previousMemberTitle, conseillers généraux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousMemberTitle Context triple: [Conseil départemental (France), previousMemberTitle, conseillers généraux]
-
A.
previousTitle
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
-
B.
formerMemberName
Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
-
C.
predecessorTitleHolder
Indicates that one entity previously held a particular title or position before another entity.
-
D.
precededByOfficeTitle
chosen
Indicates that one office title directly came before another in an ordered sequence of office positions.
-
E.
memberTitle
Indicates the formal title or designation held by a member within a group, organization, or body.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 29, 2026, 8:44 p.m.