Triple
T667286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uruguay Round (1986–1994) |
E12892
|
entity |
| Predicate | expandedRulesTo |
P9292
|
FINISHED |
| Object | trade in services |
—
|
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 in services | Statement: [Uruguay Round (1986–1994), expandedRulesTo, trade in services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedRulesTo Context triple: [Uruguay Round (1986–1994), expandedRulesTo, trade in services]
-
A.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
B.
expandedAfter
Indicates that one entity increases in size, scope, or extent after another specified event or point in time.
-
C.
expandedDuring
Indicates that an entity increased in size, scope, or extent over the course of a specified time period or event.
-
D.
expandedProtectionTo
chosen
Indicates that an existing protection, safeguard, or coverage was broadened to include an additional entity, group, area, or scope.
-
E.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff7ca788190bef58ce46849b9d0 |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.