Triple
T4836621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Protection Force |
E108074
|
entity |
| Predicate | dateOfResolution |
P2818
|
FINISHED |
| Object | 1992-02-21 |
—
|
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: 1992-02-21 | Statement: [United Nations Protection Force, dateOfResolution, 1992-02-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfResolution Context triple: [United Nations Protection Force, dateOfResolution, 1992-02-21]
-
A.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
-
B.
disputeResolvedIn
Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
-
C.
concludedAt
chosen
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
D.
appealDate
Indicates the date on which an appeal is formally filed, recorded, or scheduled in relation to a decision or case.
-
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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.