Triple
T31093191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar–Bahrain relations |
E792446
|
entity |
| Predicate | icjJudgmentYear |
P171139
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Qatar–Bahrain relations, icjJudgmentYear, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: icjJudgmentYear Context triple: [Qatar–Bahrain relations, icjJudgmentYear, 2001]
-
A.
ICJDecision
Indicates that a decision, judgment, or ruling has been issued by the International Court of Justice concerning a dispute or legal question between parties.
-
B.
legalCaseHeParticipatedInDecisionYear
Indicates the year in which he participated in making the decision in a particular legal case.
-
C.
ICJCaseName
Indicates that a particular legal case is identified by a specific official name as recognized by the International Court of Justice (ICJ).
-
D.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
E.
dateOfICTYAppealsJudgment
Indicates the calendar date on which the ICTY Appeals Chamber issued its final judgment in a given case.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 9:02 p.m.