Triple
T29924327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICJ General List No. 132 |
E760037
|
entity |
| Predicate | shortCaseName |
P130409
|
FINISHED |
| Object | Romania v. Ukraine |
—
|
NE NERFINISHED |
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: Romania v. Ukraine | Statement: [ICJ General List No. 132, shortCaseName, Romania v. Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortCaseName Context triple: [ICJ General List No. 132, shortCaseName, Romania v. Ukraine]
-
A.
shortFormat
Indicates that something is presented in a condensed or abbreviated form compared to its full or standard representation.
-
B.
isShortName
Indicates that one name is an abbreviated or shorter form of another name.
-
C.
shortDesignation
chosen
Indicates that one entity serves as a brief or abbreviated designation (such as a short name, code, or label) for another entity.
-
D.
shortFormType
Indicates that one entity is a shortened, abbreviated, or otherwise condensed form or variant of another entity.
-
E.
shortNameInJapanese
Indicates that an entity has a specific abbreviated or shorter form of its name expressed in the Japanese language.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67795fdd4819088f3c7d0de598699 |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:15 p.m.