Triple
T25300951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evian negotiations |
E634341
|
entity |
| Predicate | yearOfKeyAgreement |
P117579
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Evian negotiations, yearOfKeyAgreement, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfKeyAgreement Context triple: [Evian negotiations, yearOfKeyAgreement, 1962]
-
A.
agreementYear
chosen
Indicates the calendar year in which an agreement between the related entities was made, signed, or came into effect.
-
B.
yearOfMeeting
Indicates the specific calendar year in which the meeting between the referenced entities took place.
-
C.
yearOfKeyReview
Indicates the specific calendar year in which a key review or critical evaluation took place.
-
D.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
E.
acquisitionAgreementYear
Indicates the calendar year in which an acquisition agreement between entities was made or came into effect.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 1:24 p.m.