Triple
T26029528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanawha |
E647389
|
entity |
| Predicate | operatedByCompanyShortLived |
P188765
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kanawha, operatedByCompanyShortLived, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedByCompanyShortLived Context triple: [Kanawha, operatedByCompanyShortLived, true]
-
A.
operatedByCompany
Indicates that an entity is run, managed, or controlled by a specific company.
-
B.
operatingCompanyAbbreviation
Indicates that the object is an abbreviated or shortened form of the name of the company that operates the subject.
-
C.
operatedByCompanyInstanceOf
Indicates that an operation or activity is carried out by a specific company that is an instance of a particular company type or class.
-
D.
operatedByCompanyHeadquarteredIn
Indicates that an entity is operated by a company whose headquarters is located in a specified place.
-
E.
alsoOperatedBy
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: April 22, 2026, 9:06 a.m.