Triple
T660025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 678 |
E11732
|
entity |
| Predicate | deadlineForCompliance |
P8546
|
FINISHED |
| Object | 1991-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: 1991-01-15 | Statement: [UN Security Council Resolution 678, deadlineForCompliance, 1991-01-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadlineForCompliance Context triple: [UN Security Council Resolution 678, deadlineForCompliance, 1991-01-15]
-
A.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
commitmentTiming
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
-
C.
statuteOfLimitations
Indicates that there is a legally defined time limit within which a claim, charge, or legal action related to an event must be initiated.
-
D.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d1406ec8190abf546549264c85d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.