Triple
T3389736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTO Appellate Body |
E71387
|
entity |
| Predicate | averageAppealDurationLimit |
P7618
|
FINISHED |
| Object | 60 days |
—
|
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: 60 days | Statement: [WTO Appellate Body, averageAppealDurationLimit, 60 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageAppealDurationLimit Context triple: [WTO Appellate Body, averageAppealDurationLimit, 60 days]
-
A.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
B.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
-
C.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
timeBetweenAnnouncementAndTermination
Indicates the duration of time that elapses between when something is officially announced and when it is subsequently terminated.
-
E.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
- 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_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. |
Created at: March 8, 2026, 3:14 p.m.