Triple
T25564048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 1037 |
E640787
|
entity |
| Predicate | mandateStart |
P86265
|
FINISHED |
| Object | 1996-01-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: 1996-01-15 | Statement: [UN Security Council Resolution 1037, mandateStart, 1996-01-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandateStart Context triple: [UN Security Council Resolution 1037, mandateStart, 1996-01-15]
-
A.
mandateStartYear
Indicates the year in which a mandate or required obligation officially begins.
-
B.
mandateFrom
Indicates that one entity has been granted authoritative permission or instruction by another entity to act or decide on its behalf.
-
C.
mandateStartDateForUNMIL
chosen
Indicates the date on which the official mandate for UNMIL (the United Nations Mission in Liberia) begins.
-
D.
mandateDefinedBy
Indicates that the scope, authority, or responsibilities of one entity’s mandate are formally established or specified by another entity or source.
-
E.
mandateConfirmedDate
Indicates the date on which a mandate (such as an authorization or directive) was formally confirmed or validated.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8fb94b48190b135b603667279a7 |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 3:48 p.m.