Triple
T5035475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Coronel |
E113409
|
entity |
| Predicate | keyExport |
P60636
|
FINISHED |
| Object | forestry products |
—
|
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: forestry products | Statement: [Port of Coronel, keyExport, forestry products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyExport Context triple: [Port of Coronel, keyExport, forestry products]
-
A.
keyExperiment
Indicates that an experiment plays a central or pivotal role within a broader study, project, or research context.
-
B.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
C.
keyOperation
Indicates an operation that is central, primary, or essential to the functioning or outcome of another process, system, or relationship.
-
D.
keyText
Indicates that a piece of text functions as a key or identifier used to access, reference, or unlock something in a system or context.
-
E.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73b9ad488190a2a8c4da8858eb91 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd724ff2b4819091351cf80d3647a1 |
completed | March 20, 2026, 4:14 p.m. |
Created at: March 20, 2026, 1:36 p.m.