Triple
T34027194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consol Energy |
E872540
|
entity |
| Predicate | majorCustomerSector |
P143750
|
FINISHED |
| Object | electric power utilities |
—
|
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: electric power utilities | Statement: [Consol Energy, majorCustomerSector, electric power utilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCustomerSector Context triple: [Consol Energy, majorCustomerSector, electric power utilities]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
typicalConstituentSector
Indicates that something is a usual or characteristic sector that forms part of a larger whole or system.
-
C.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
D.
economicSectors
chosen
Indicates a relationship that associates entities with the economic sectors or industries in which they operate or to which they belong.
-
E.
sectoralExample
Indicates that something serves as a representative or illustrative example within a particular sector or industry context.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, 1:51 a.m.