Triple
T29487392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 1810 |
E747967
|
entity |
| Predicate | extendsMandateUntil |
P32455
|
FINISHED |
| Object | 2011-04-25 |
—
|
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: 2011-04-25 | Statement: [UN Security Council Resolution 1810, extendsMandateUntil, 2011-04-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsMandateUntil Context triple: [UN Security Council Resolution 1810, extendsMandateUntil, 2011-04-25]
-
A.
extensionEffectiveDate
chosen
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
B.
extendedAuthorityTo
Indicates that one entity has granted or delegated its decision-making power or control to another entity.
-
C.
leaseExtendedUntil
Indicates that an existing lease agreement has been prolonged so that its validity now continues up to a specified end date.
-
D.
extendsCopyrightTermFor
Indicates that one entity lengthens the duration of copyright protection granted to another entity or its work.
-
E.
extendedOversightTo
Indicates that one entity has broadened or expanded its supervisory or regulatory authority to include another entity or domain.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c06bbc48190b97efd782ebc81e6 |
completed | May 2, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:10 p.m.