Triple
T14262965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTO document WT/DS512/R |
E353570
|
entity |
| Predicate | WTObody |
P113444
|
FINISHED |
| Object | Panel |
—
|
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: Panel | Statement: [WTO document WT/DS512/R, WTObody, Panel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WTObody Context triple: [WTO document WT/DS512/R, WTObody, Panel]
-
A.
WTOBody
chosen
Indicates that an entity is a formal organ, committee, or decision-making body within the institutional structure of the World Trade Organization.
-
B.
WTOBodyAdoptingReport
Indicates that a WTO decision-making body has formally adopted a report as an official and binding outcome of a dispute or review process.
-
C.
WTOCaseCode
Indicates that there is an association between an entity and a specific World Trade Organization dispute or case identified by its official case code.
-
D.
WTOAgreementInvoked
Indicates that a World Trade Organization agreement has been formally cited or relied upon as a legal basis or reference in a given context or dispute.
-
E.
treatyBody
Indicates that one entity functions as an official treaty-monitoring or treaty-implementing body in relation to a specific treaty or agreement.
- 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_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:09 a.m.