Triple
T35465871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chile–Bolivia transport network |
E1025070
|
entity |
| Predicate | facilitatesExport |
P47461
|
FINISHED |
| Object | Bolivian minerals |
—
|
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: Bolivian minerals | Statement: [Chile–Bolivia transport network, facilitatesExport, Bolivian minerals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facilitatesExport Context triple: [Chile–Bolivia transport network, facilitatesExport, Bolivian minerals]
-
A.
supportsImportExport
Indicates that one entity provides functionality for importing and exporting data or resources to and from another entity.
-
B.
exportedTo
Indicates that goods, services, or resources are sent out from one entity or region to another for trade or sale.
-
C.
isExportable
Indicates that something can be legally and practically transferred or sent out from one jurisdiction, system, or context to another.
-
D.
isExported
Indicates that an entity is sent out or transferred from its origin to an external destination or system.
-
E.
exportedVia
chosen
Indicates that something is sent out or made available to an external destination through a specified medium, channel, or mechanism.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.