Triple
T3389717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTO Appellate Body |
E71387
|
entity |
| Predicate | lostQuorumOn |
P47188
|
FINISHED |
| Object | 2019-12-11 |
—
|
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: 2019-12-11 | Statement: [WTO Appellate Body, lostQuorumOn, 2019-12-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostQuorumOn Context triple: [WTO Appellate Body, lostQuorumOn, 2019-12-11]
-
A.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
B.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
C.
lostEffectiveControlOf
Indicates that an entity no longer has practical or functional authority, influence, or command over another entity, asset, or domain, even if formal or legal control may still exist.
-
D.
hasQuorum
Indicates that the number of required participants or members is sufficient to validly conduct the specified activity or decision.
-
E.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb666e514819090560d43bfaf55b8 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada527ff308190813a7ffdcdec4322 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.