Triple
T9685000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 1963 |
E234383
|
entity |
| Predicate | mandateExtensionUntil |
P41751
|
FINISHED |
| Object | 2013-12-31 |
—
|
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: 2013-12-31 | Statement: [United Nations Security Council Resolution 1963, mandateExtensionUntil, 2013-12-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandateExtensionUntil Context triple: [United Nations Security Council Resolution 1963, mandateExtensionUntil, 2013-12-31]
-
A.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
B.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
C.
extendsUntil
chosen
Indicates that something continues or remains in effect up to a specified point or limit in time or space.
-
D.
mandateExpanded
Indicates that an entity’s scope of authority, responsibility, or mission has been broadened beyond its previous mandate.
-
E.
mandateFrom
Indicates that one entity has been granted authoritative permission or instruction by another entity to act or decide on its behalf.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9cd0877c81909fde1989d946aae9 |
completed | April 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:16 p.m.