Triple
T216616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marrakesh Agreement Establishing the World Trade Organization |
E4118
|
entity |
| Predicate | concludedDate |
P140
|
FINISHED |
| Object | 1994-04-15 |
—
|
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: 1994-04-15 | Statement: [Marrakesh Agreement Establishing the World Trade Organization, concludedDate, 1994-04-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludedDate Context triple: [Marrakesh Agreement Establishing the World Trade Organization, concludedDate, 1994-04-15]
-
A.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
B.
concludedAtEvent
Indicates that an entity’s participation, state, or validity ended as a result of a specific event.
-
C.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
D.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.