Triple
T7277428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratko Mladić |
E163063
|
entity |
| Predicate | extraditionDate |
P35581
|
FINISHED |
| Object | 2011-05-31 |
—
|
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-05-31 | Statement: [Ratko Mladić, extraditionDate, 2011-05-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extraditionDate Context triple: [Ratko Mladić, extraditionDate, 2011-05-31]
-
A.
dateOfExtradition
chosen
Indicates the date on which an individual or entity is formally transferred from one jurisdiction to another under an extradition process.
-
B.
countryOfExtradition
Indicates the country to which a person is or may be surrendered under an extradition process.
-
C.
reentryDate
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
D.
extraditionDirection
Indicates the direction in which an extradition process is occurring, specifying from which jurisdiction a person is being surrendered and to which jurisdiction they are being transferred.
-
E.
dateOfExfiltration
Indicates the specific date on which data or information was illicitly removed or extracted from its original location.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.