Triple
T567319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article XXI (Security Exceptions) |
E13582
|
entity |
| Predicate | invocableBy |
P4794
|
FINISHED |
| Object | any WTO member state |
—
|
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: any WTO member state | Statement: [Article XXI (Security Exceptions), invocableBy, any WTO member state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invocableBy Context triple: [Article XXI (Security Exceptions), invocableBy, any WTO member state]
-
A.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
B.
calledBy
Indicates that one entity initiates a call or invocation to another entity.
-
C.
callsFor
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
D.
canBeCalledInto
Indicates that one entity has the authority or ability to summon, request the presence of, or formally convene another entity.
-
E.
appliedBy
chosen
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b02da148190b6a9bad3a22d8ec5 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.