Triple
T13930006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 16e législature de la Ve République |
E334964
|
entity |
| Predicate | précédéePar |
P25144
|
FINISHED |
| Object | 15e législature de la Ve République |
—
|
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: 15e législature de la Ve République | Statement: [16e législature de la Ve République, précédéePar, 15e législature de la Ve République]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: précédéePar Context triple: [16e législature de la Ve République, précédéePar, 15e législature de la Ve République]
-
A.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
B.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
D.
precedesDisc
Indicates that one discourse segment or unit occurs before another in the sequence of discourse.
-
E.
classPrecededBy
Indicates that one class occurs or is scheduled before another class in a sequence or timetable.
- 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.