Triple
T13930012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 16e législature de la Ve République |
E334964
|
entity |
| Predicate | début |
P19545
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [16e législature de la Ve République, début, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: début Context triple: [16e législature de la Ve République, début, 2022]
-
A.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
B.
testDebutFor
Indicates that an entity makes its first appearance or performance in a particular test event, context, or setting.
-
C.
isDebut
Indicates that something is the first formal appearance or introduction of an entity, such as a person, work, or performance, in a particular context or domain.
-
D.
labelDebutOf
Indicates the event, work, or context in which an entity (such as an artist, character, or product) first officially appears or is introduced.
-
E.
debutFeatureOf
Indicates that one entity is the first major or initial feature (such as a debut work or appearance) associated with another entity.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa900a0819095eeb1bc46b0336e |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.