Triple
T9460476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaranj |
E228131
|
entity |
| Predicate | borderTradeIncludes |
P46598
|
FINISHED |
| Object | fuel |
—
|
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: fuel | Statement: [Zaranj, borderTradeIncludes, fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTradeIncludes Context triple: [Zaranj, borderTradeIncludes, fuel]
-
A.
borderTradeType
Indicates the specific category or nature of trade that occurs across a border between two regions or countries.
-
B.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
C.
tradeBloc
Indicates a formal economic relationship in which entities participate together in a trade bloc, coordinating trade policies and often reducing barriers to commerce among members.
-
D.
customsAssociated
Indicates that certain cultural or social customs are connected with, practiced by, or characteristic of a particular entity.
-
E.
importedCommodity
chosen
Indicates that a commodity has been brought into a country or region from abroad through import activities.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcaf610819092bcd3b871665aa5 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.