Triple
T32082800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lead I |
E819343
|
entity |
| Predicate | isStandardLimbLead |
P32622
|
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: [Lead I, isStandardLimbLead, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandardLimbLead Context triple: [Lead I, isStandardLimbLead, true]
-
A.
hasEinthovenNumber
Indicates the association of an entity with a specific Einthoven number, typically identifying its position or type within Einthoven’s classification system (e.g., for ECG leads).
-
B.
isStandard
chosen
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
C.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
isStandardInInstrument
Indicates that something conforms to the usual or officially accepted form, configuration, or usage within a given instrument.
-
E.
hasNumberOfElectrodes
Indicates the relationship that specifies how many electrodes are associated with a given 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:24 a.m.