Triple
T24522870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banana |
E606581
|
entity |
| Predicate | hasPortUse |
P156598
|
FINISHED |
| Object | export of minerals from inland Congo (historically) |
—
|
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: export of minerals from inland Congo (historically) | Statement: [Banana, hasPortUse, export of minerals from inland Congo (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortUse Context triple: [Banana, hasPortUse, export of minerals from inland Congo (historically)]
-
A.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
B.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
-
C.
usedOnPort
Indicates that something is applied, connected, or operates specifically on a given port.
-
D.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
-
E.
hasUserPort
Indicates that an entity is associated with, exposes, or is accessible through a specific user-facing port or interface.
- F. None of above. chosen
Provenance (4 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:25 a.m.