Triple
T14262972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTO document WT/DS512/R |
E353570
|
entity |
| Predicate | caseCode |
P76198
|
FINISHED |
| Object | DS512 |
—
|
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: DS512 | Statement: [WTO document WT/DS512/R, caseCode, DS512]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseCode Context triple: [WTO document WT/DS512/R, caseCode, DS512]
-
A.
caseNumber
chosen
Indicates the unique identifying number assigned to a particular legal or administrative case.
-
B.
caseTypes
Indicates the types or categories of cases associated with or applicable to an entity or situation.
-
C.
scriptCodeCase
Indicates how the script code is represented with respect to letter casing (e.g., uppercase, lowercase, or mixed case).
-
D.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
E.
courtCode
Indicates the specific court or judicial body associated with a legal case, proceeding, or record.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de63563fc88190b0abdbf8529c65eb |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:09 a.m.