Triple
T29924352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICJ General List No. 132 |
E760037
|
entity |
| Predicate | bindingOnParties |
P113545
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ICJ General List No. 132, bindingOnParties, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindingOnParties Context triple: [ICJ General List No. 132, bindingOnParties, yes]
-
A.
addressesParties
Indicates that one entity formally directs communication, documentation, or statements to specific parties as their intended recipients.
-
B.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
C.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
D.
bindingOnSignatories
chosen
Indicates that an agreement, rule, or obligation is legally or formally enforceable upon all parties who have signed it.
-
E.
collaboratingParty
Indicates that an entity is actively working together with another entity toward a shared goal, project, or activity.
- 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_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:15 p.m.