Triple
T32082808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lead I |
E819343
|
entity |
| Predicate | hasPositiveElectrode |
P32373
|
FINISHED |
| Object | left arm |
—
|
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: left arm | Statement: [Lead I, hasPositiveElectrode, left arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositiveElectrode Context triple: [Lead I, hasPositiveElectrode, left arm]
-
A.
hasElectrode
Indicates that one entity is equipped with, contains, or is associated with an electrode component.
-
B.
electrodeType
Indicates the specific kind or classification of an electrode associated with an entity or used in a given context.
-
C.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
D.
hasElectrodeReaction
Indicates that an electrochemical system or component undergoes a specific chemical reaction at one of its electrodes.
-
E.
electricalPolarity
chosen
Indicates that there is a relationship specifying the direction or type of electrical charge or potential difference associated with an entity or connection.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 1, 2026, 12:24 a.m.