Triple
T3770309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voltaic pile |
E82780
|
entity |
| Predicate | electrodeMaterial |
P618
|
FINISHED |
| Object | zinc |
—
|
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: zinc | Statement: [Voltaic pile, electrodeMaterial, zinc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electrodeMaterial Context triple: [Voltaic pile, electrodeMaterial, zinc]
-
A.
electrodeType
Indicates the specific kind or classification of an electrode associated with an entity or used in a given context.
-
B.
hasElectrode
Indicates that one entity is equipped with, contains, or is associated with an electrode component.
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
electricalConductivity
Indicates that one entity has the ability to conduct electric current through it, typically quantified as a measure of how easily charge flows within that material or medium.
-
E.
material
chosen
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2f016c81909c2e3c85dbc3c259 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.