Triple
T13930024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 16e législature de la Ve République |
E334964
|
entity |
| Predicate | sujetDe |
P450
|
FINISHED |
| Object | négociations parlementaires renforcées |
—
|
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: négociations parlementaires renforcées | Statement: [16e législature de la Ve République, sujetDe, négociations parlementaires renforcées]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sujetDe Context triple: [16e législature de la Ve République, sujetDe, négociations parlementaires renforcées]
-
A.
subjectMatter
chosen
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
B.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
C.
subjectOfProject
Indicates that an entity serves as the main focus, topic, or target of a particular project.
-
D.
subjectMVP
Indicates that the subject is considered the most valuable player (MVP) in a given context or event.
-
E.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
- 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.