Triple
T29769167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Comtrade database |
E753997
|
entity |
| Predicate | providesMeasure |
P29129
|
FINISHED |
| Object | trade value |
—
|
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 value | Statement: [UN Comtrade database, providesMeasure, trade value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesMeasure Context triple: [UN Comtrade database, providesMeasure, trade value]
-
A.
containsMeasure
Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
-
B.
includesMeasure
chosen
Indicates that one entity contains, incorporates, or makes use of a particular measurement or quantitative value as part of its definition or specification.
-
C.
measureOf
Indicates that one entity serves as a quantitative or qualitative assessment or metric describing a property, extent, or magnitude of another entity.
-
D.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
E.
implementsMeasure
Indicates that one entity carries out, applies, or realizes a specified measure, policy, or procedure.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 28, 2026, 8:40 p.m.