Triple
T26520151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copper River and Northwestern Railway |
E669927
|
entity |
| Predicate | commodityCarried |
P124266
|
FINISHED |
| Object | copper ore |
—
|
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: copper ore | Statement: [Copper River and Northwestern Railway, commodityCarried, copper ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commodityCarried Context triple: [Copper River and Northwestern Railway, commodityCarried, copper ore]
-
A.
cargoContents
chosen
Indicates that one entity contains or carries another entity as its cargo.
-
B.
commonlyTransportedIn
Indicates that something is usually carried, moved, or conveyed using a particular vehicle, container, or mode of transport.
-
C.
cargoQuantity
Indicates the amount or volume of cargo associated with a shipment, transport, or storage event.
-
D.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
E.
cargoHoldType
Indicates the specific type or classification of a cargo hold associated with an entity.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 1:27 a.m.