Triple
T5633903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTO agreements |
E147897
|
entity |
| Predicate | includePrinciple |
P64704
|
FINISHED |
| Object | tariff binding and reduction |
—
|
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: tariff binding and reduction | Statement: [WTO agreements, includePrinciple, tariff binding and reduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includePrinciple Context triple: [WTO agreements, includePrinciple, tariff binding and reduction]
-
A.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
B.
implementsPrinciple
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
C.
recognizesPrinciple
Indicates that an entity acknowledges the validity, authority, or applicability of a particular principle.
-
D.
establishesPrinciple
Indicates that an entity formulates, defines, or sets forth a foundational rule, guideline, or standard that others are expected to follow or build upon.
-
E.
supportsPrinciple
Indicates that one entity endorses, upholds, or actively backs a particular principle or doctrine.
- F. None of above. chosen
Provenance (4 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225ff3248190b93c9f5887553fd4 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:41 p.m.