Triple
T3613711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosnia and Herzegovina v. Serbia and Montenegro (ICJ, 2007) |
E76548
|
entity |
| Predicate | dateOfJudgment |
P2232
|
FINISHED |
| Object | 2007-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: 2007-02-26 | Statement: [Bosnia and Herzegovina v. Serbia and Montenegro (ICJ, 2007), dateOfJudgment, 2007-02-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfJudgment Context triple: [Bosnia and Herzegovina v. Serbia and Montenegro (ICJ, 2007), dateOfJudgment, 2007-02-26]
-
A.
dateOfLastJudgment
Indicates the specific date on which the most recent formal judgment or decision was rendered in a given case or proceeding.
-
B.
decisionDate
chosen
Indicates the date on which a specific decision was formally made or finalized.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
trialDate
Indicates the specific calendar date on which a legal trial or court proceeding is scheduled or took place.
-
E.
sentencedOn
Indicates that a judicial authority has formally imposed a legal sentence or punishment on an entity on a specific date.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2786f808190be4e42734a79d74e |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.