Triple
T14692528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libya situation at the ICC |
E345069
|
entity |
| Predicate | referralDate |
P115364
|
FINISHED |
| Object | 2011-02-26 |
—
|
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: 2011-02-26 | Statement: [Libya situation at the ICC, referralDate, 2011-02-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referralDate Context triple: [Libya situation at the ICC, referralDate, 2011-02-26]
-
A.
revenueDate
Indicates the date on which revenue is recognized, recorded, or attributed in relation to a transaction or financial event.
-
B.
admissionDate
Indicates the date on which an entity (such as a person, application, or item) is formally admitted, accepted, or entered into a system or institution.
-
C.
acknowledgmentDate
Indicates the date on which an acknowledgment of something (such as receipt, notice, or information) is formally recorded or recognized.
-
D.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
E.
recommendedDate
Indicates the date on which something is advised or suggested to occur, be used, or be acted upon.
- F. None of above. chosen
Provenance (4 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb585d46c81908d6964130914cec4 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.