Triple
T34811014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes Carbon Corporation |
E1003496
|
entity |
| Predicate | suppliesToIndustry |
P73591
|
FINISHED |
| Object | steel industry |
—
|
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: steel industry | Statement: [Great Lakes Carbon Corporation, suppliesToIndustry, steel industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliesToIndustry Context triple: [Great Lakes Carbon Corporation, suppliesToIndustry, steel industry]
-
A.
suppliesIndustry
chosen
Indicates that one entity provides goods, services, or resources to support the operations or needs of an industry or industrial sector.
-
B.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
C.
supportedIndustry
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
D.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
E.
usedInIndustry
Indicates that something is employed or applied within a particular industry or industrial sector.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ab4a9dc8190ad41fb613f35ddad |
completed | May 3, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.