Triple
T23588884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall–Héroult process |
E582418
|
entity |
| Predicate | anodeType |
P32371
|
FINISHED |
| Object | consumable anodes |
—
|
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: consumable anodes | Statement: [Hall–Héroult process, anodeType, consumable anodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anodeType Context triple: [Hall–Héroult process, anodeType, consumable anodes]
-
A.
anodeMaterial
Indicates that one entity serves as the material from which the anode of another entity is made.
-
B.
anodeFunction
Indicates that something serves as or relates to the functional role of an anode within an electrical or electrochemical system.
-
C.
electrodeType
chosen
Indicates the specific kind or classification of an electrode associated with an entity or used in a given context.
-
D.
anatomicalType
Indicates that one entity is classified as a specific anatomical category or kind of anatomical structure in relation to another.
-
E.
ATUType
Indicates a classification relationship where an item is assigned a specific Aarne–Thompson–Uther (ATU) folktale type.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0336aec8190856aee4a8273c3e5 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.