Triple
T33341260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Owendo |
E853673
|
entity |
| Predicate | usedForExportOf |
P47461
|
FINISHED |
| Object | manganese |
—
|
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: manganese | Statement: [Port of Owendo, usedForExportOf, manganese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForExportOf Context triple: [Port of Owendo, usedForExportOf, manganese]
-
A.
exportedTo
Indicates that goods, services, or resources are sent out from one entity or region to another for trade or sale.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
isExported
Indicates that an entity is sent out or transferred from its origin to an external destination or system.
-
D.
exportedVia
chosen
Indicates that something is sent out or made available to an external destination through a specified medium, channel, or mechanism.
-
E.
exportedGood
Indicates that a good has been sent out from one country or region to another as part of international trade.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:34 a.m.