Triple
T450357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trade Policy Review Mechanism |
E7112
|
entity |
| Predicate | frequencyDependsOn |
P13344
|
FINISHED |
| Object | member’s share in world trade |
—
|
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: member’s share in world trade | Statement: [Trade Policy Review Mechanism, frequencyDependsOn, member’s share in world trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyDependsOn Context triple: [Trade Policy Review Mechanism, frequencyDependsOn, member’s share in world trade]
-
A.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
B.
frequencyComparedTo
Indicates how often one event or action occurs relative to another, expressing a comparison of their frequencies.
-
C.
frequencyRequirement
Indicates a constraint specifying how often an action, event, or condition must occur within a given context or time frame.
-
D.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
E.
selectionRankingFrequency
Indicates how often an entity is chosen or ranked in a particular position within a selection or ordering process.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef691cc8819091729eaac52c9457 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.