Triple
T22769572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GAFTA |
E563216
|
entity |
| Predicate | barrierTypeAddressed |
P53911
|
FINISHED |
| Object | tariff barriers |
—
|
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: tariff barriers | Statement: [GAFTA, barrierTypeAddressed, tariff barriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barrierTypeAddressed Context triple: [GAFTA, barrierTypeAddressed, tariff barriers]
-
A.
typicalBarrierType
chosen
Indicates the usual or characteristic type of barrier associated with or used in a given context or situation.
-
B.
isBarrierTo
Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
-
C.
barrierBrokenIn
Indicates that a barrier or obstruction has been breached, removed, or overcome within a specified context, location, or situation.
-
D.
typeOfSecurityAddressed
Indicates the category or kind of security concern, risk, or protection that is being addressed in a given context.
-
E.
barrierBreakingRole
Indicates a role in which an entity overcomes or dismantles an existing barrier, limitation, or obstacle within a given context.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b5cea44819097290351da9c488d |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:27 p.m.