Triple
T37108167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Energy Corporation |
E918906
|
entity |
| Predicate | impliesSector |
P2193
|
FINISHED |
| Object | energy sector |
—
|
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: energy sector | Statement: [Energy Corporation, impliesSector, energy sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesSector Context triple: [Energy Corporation, impliesSector, energy sector]
-
A.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
-
B.
targetsSector
Indicates that an entity is directed toward, focused on, or intended to affect a particular economic or industry sector.
-
C.
sectoralExample
Indicates that something serves as a representative or illustrative example within a particular sector or industry context.
-
D.
sectorServed
chosen
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
E.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:14 p.m.