Triple
T33860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Court of Justice |
E674
|
entity |
| Predicate | canHearCasesFrom |
P1032
|
FINISHED |
| Object | sovereign states only |
—
|
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: sovereign states only | Statement: [International Court of Justice, canHearCasesFrom, sovereign states only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHearCasesFrom Context triple: [International Court of Justice, canHearCasesFrom, sovereign states only]
-
A.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
B.
appealsFrom
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
C.
hasNumberOfCasesApprox
Indicates that an entity is associated with an approximate (not exact) count of cases.
-
D.
hasOriginalJurisdictionOver
chosen
Indicates that a legal body or authority has the power to hear and decide a case first, before any appellate review by higher bodies.
-
E.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2496ffc548190b545f998cbebd5b9 |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a248717f5081909952a8c9ed1e1742 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.