Triple
T7052171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutional Council of France |
E163991
|
entity |
| Predicate | introducedQPC |
P8259
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Constitutional Council of France, introducedQPC, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedQPC Context triple: [Constitutional Council of France, introducedQPC, 2010]
-
A.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
B.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
C.
introducedPart
Indicates that one entity has brought another entity into existence, use, or awareness as a component or element of something.
-
D.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
E.
engineIntroduced
Indicates that a particular engine was first introduced or brought into use at a specific time or in a specific context.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.