Triple
T313853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kampala Amendments |
E7663
|
entity |
| Predicate | endDateOfConference |
P140
|
FINISHED |
| Object | 2010-06-11 |
—
|
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: 2010-06-11 | Statement: [Kampala Amendments, endDateOfConference, 2010-06-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endDateOfConference Context triple: [Kampala Amendments, endDateOfConference, 2010-06-11]
-
A.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
concludedAtEvent
Indicates that an entity’s participation, state, or validity ended as a result of a specific event.
-
C.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
D.
officeEnded
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
E.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4bd6a081909bdb57602c7093b4 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.