Triple
T4695620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Mission in Sierra Leone |
E104133
|
entity |
| Predicate | securityCouncilResolutionDate |
P4731
|
FINISHED |
| Object | 1999-10-22 |
—
|
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: 1999-10-22 | Statement: [United Nations Mission in Sierra Leone, securityCouncilResolutionDate, 1999-10-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityCouncilResolutionDate Context triple: [United Nations Mission in Sierra Leone, securityCouncilResolutionDate, 1999-10-22]
-
A.
UNResolutionDate
chosen
Indicates the calendar date on which a specific United Nations resolution was formally adopted or passed.
-
B.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
C.
ratifiedAt
Indicates the date, time, or event context at which an agreement, treaty, or formal decision was officially ratified.
-
D.
ratifiedOn
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
-
E.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.