Triple
T20564590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economic Partnership Agreements |
E504933
|
entity |
| Predicate | startOfNegotiations |
P72289
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Economic Partnership Agreements, startOfNegotiations, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfNegotiations Context triple: [Economic Partnership Agreements, startOfNegotiations, 2002]
-
A.
negotiationStart
chosen
Indicates the point in time or event at which a negotiation process between parties begins.
-
B.
negotiationPhase
Indicates the specific stage or step currently reached within an ongoing negotiation process between parties.
-
C.
negotiatesOver
Indicates that one entity engages in discussion or bargaining with another entity concerning the terms, conditions, or details of a specific subject or item.
-
D.
negotiationRound
Indicates a specific stage or iteration within an ongoing negotiation process between parties.
-
E.
positionOnNegotiations
Indicates the stance or viewpoint an entity holds regarding a particular negotiation or set of negotiations.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a15c988190ba93823df119ca4d |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.