Triple
T27489628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usibelli Coal Mine |
E693842
|
entity |
| Predicate | hasCoalReserves |
P113231
|
FINISHED |
| Object | Healy coal field |
—
|
NE NERFINISHED |
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: Healy coal field | Statement: [Usibelli Coal Mine, hasCoalReserves, Healy coal field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoalReserves Context triple: [Usibelli Coal Mine, hasCoalReserves, Healy coal field]
-
A.
hasCoalBasin
Indicates that one entity contains, includes, or is characterized by a coal-bearing geological basin associated with the other entity.
-
B.
hasCoalMineNearby
Indicates that a location or entity is situated close to at least one coal mine.
-
C.
hasCoalMiningCompany
Indicates that an entity is associated with or owns a company whose primary business is coal mining.
-
D.
hasCoalMiningHistory
Indicates that an entity has a past or ongoing involvement in coal mining activities or industry.
-
E.
isCoalBearing
chosen
Indicates that the subject contains or is associated with coal deposits or coal-bearing formations.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: April 27, 2026, 1:04 p.m.