Triple
T23946906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matignon Accords process |
E602936
|
entity |
| Predicate | keySignatory |
P45747
|
FINISHED |
| Object | Michel Rocard |
—
|
NE NERFINISHED |
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: Michel Rocard | Statement: [Matignon Accords process, keySignatory, Michel Rocard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySignatory Context triple: [Matignon Accords process, keySignatory, Michel Rocard]
-
A.
signatoryAuthority
Indicates that an entity has the legal power or authorization to sign documents or agreements on behalf of another party.
-
B.
signerOf
chosen
Indicates that an entity has signed or formally endorsed a document, agreement, or statement.
-
C.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
D.
laterSignatory
Indicates that one party signed or agreed to something at a later time than another specified party.
-
E.
signatoryLeader
Indicates that a leader has formally signed or endorsed an agreement, treaty, or document on behalf of a group, organization, or state.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02ee0288190b58fd71b9cc65964 |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:16 p.m.