Triple
T2934880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Green Bay |
E79240
|
entity |
| Predicate | handlesCommodity |
P44036
|
FINISHED |
| Object | coal |
—
|
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: coal | Statement: [Port of Green Bay, handlesCommodity, coal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesCommodity Context triple: [Port of Green Bay, handlesCommodity, coal]
-
A.
commodity
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
B.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
C.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
D.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
E.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983c84688190aa7ed5b8091fb140 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:56 p.m.