Triple
T4753528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTO Secretariat |
E105531
|
entity |
| Predicate | hasNoDecisionMakingPowerOn |
P24117
|
FINISHED |
| Object | trade disputes |
—
|
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: trade disputes | Statement: [WTO Secretariat, hasNoDecisionMakingPowerOn, trade disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoDecisionMakingPowerOn Context triple: [WTO Secretariat, hasNoDecisionMakingPowerOn, trade disputes]
-
A.
hasDecisionMakingPower
Indicates that one entity possesses the authority or ability to make decisions that affect another entity or a given context.
-
B.
hasNoPowerOver
chosen
Indicates that one entity lacks authority, control, or influence over another entity or situation.
-
C.
hasDecisionMaker
Indicates that one entity serves as the decision-making authority or agent for another entity.
-
D.
hasLimitedAuthorityOver
Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
-
E.
hasNotableDecision
Indicates that an entity is associated with a specific decision that is considered significant or noteworthy in some context.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e72d1c81908eb60960751e52b1 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.