Triple
T30946171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coal Creek |
E788397
|
entity |
| Predicate | hasPrimaryEmployment |
P200096
|
FINISHED |
| Object | coal mining |
—
|
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 mining | Statement: [Coal Creek, hasPrimaryEmployment, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryEmployment Context triple: [Coal Creek, hasPrimaryEmployment, coal mining]
-
A.
hasPrimarySectorEmployment
chosen
Indicates that an entity is employed in the primary economic sector (e.g., agriculture, mining, forestry, or related extractive activities).
-
B.
employedForWork
Indicates that one entity works for another entity in an employment relationship, performing labor or services in exchange for compensation.
-
C.
employsOrEmployed
Indicates that one entity currently employs or previously employed another entity in a work or service relationship.
-
D.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
E.
stateOfEmployment
Indicates that one entity’s employment status or condition is defined in relation to another entity (such as an employer, position, or employment situation).
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: April 29, 2026, 8:53 p.m.