Triple
T27489623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usibelli Coal Mine |
E693842
|
entity |
| Predicate | shipsTo |
P162440
|
FINISHED |
| Object | domestic customers in Alaska |
—
|
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: domestic customers in Alaska | Statement: [Usibelli Coal Mine, shipsTo, domestic customers in Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipsTo Context triple: [Usibelli Coal Mine, shipsTo, domestic customers in Alaska]
-
A.
shipsWith
Indicates that one entity is delivered, packaged, or provided together with another entity as part of the same shipment or bundle.
-
B.
sentShipsTo
Indicates that one entity dispatched or directed ships to another entity or location.
-
C.
shipCompanion
Indicates that one entity serves as a companion or partner accompanying another entity on a ship or sea voyage.
-
D.
shipFlag
Indicates that a ship is registered under and legally operates under the authority of a specified national flag or registry.
-
E.
usedShipsFrom
Indicates that one entity is the location or source from which used ships are sent, dispatched, or originate.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e882cbc81908caa3e8a5fb5c1f4 |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:04 p.m.