Triple
T14130801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 1143 |
E350159
|
entity |
| Predicate | startOfExtensionPeriod |
P61280
|
FINISHED |
| Object | 1997-12-05 |
—
|
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: 1997-12-05 | Statement: [United Nations Security Council Resolution 1143, startOfExtensionPeriod, 1997-12-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfExtensionPeriod Context triple: [United Nations Security Council Resolution 1143, startOfExtensionPeriod, 1997-12-05]
-
A.
grantPeriodStart
Indicates the date or time at which a grant’s active period or coverage begins.
-
B.
extensionOpeningPeriod
chosen
Indicates the time span during which an extension (such as a facility, service, or feature) is open or available for use.
-
C.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
D.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
E.
focusPeriodStart
Indicates the point in time at which a specified focus period or interval begins.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610aa434819096671c5aabb9134a |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:47 p.m.