Triple
T14021386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Trust Territory |
E337339
|
entity |
| Predicate | endDateEvent |
P140
|
FINISHED |
| Object | termination of United Nations trusteeship |
—
|
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: termination of United Nations trusteeship | Statement: [Strategic Trust Territory, endDateEvent, termination of United Nations trusteeship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endDateEvent Context triple: [Strategic Trust Territory, endDateEvent, termination of United Nations trusteeship]
-
A.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
organizedEventEndTime
Indicates the time at which an organized event is scheduled or recorded to end.
-
C.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
D.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
E.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3c7cd88190b236382058581740 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.