Triple
T24196594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Transitional Authority in Cambodia |
E599850
|
entity |
| Predicate | electionDates |
P102366
|
FINISHED |
| Object | 1993-05-23 to 1993-05-28 |
—
|
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: 1993-05-23 to 1993-05-28 | Statement: [United Nations Transitional Authority in Cambodia, electionDates, 1993-05-23 to 1993-05-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionDates Context triple: [United Nations Transitional Authority in Cambodia, electionDates, 1993-05-23 to 1993-05-28]
-
A.
electionDate
Indicates the specific calendar date on which an election is scheduled to be or was held.
-
B.
electionsHeldOn
chosen
Indicates that one or more elections took place on a specified date or set of dates.
-
C.
electionsScheduledFor
Indicates that a specific election is planned or set to occur at a particular time or for a particular entity.
-
D.
electionCalledDate
Indicates the date on which an election is officially announced or formally called.
-
E.
electorCountDate
Indicates the date on which the number of electors (or electoral votes) associated with an entity is determined or recorded.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24ad83c819084ac9e34d2cc2120 |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.