Triple
T32082797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lead I |
E819343
|
entity |
| Predicate | hasEinthovenNumber |
P173522
|
FINISHED |
| Object | I |
—
|
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: I | Statement: [Lead I, hasEinthovenNumber, I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEinthovenNumber Context triple: [Lead I, hasEinthovenNumber, I]
-
A.
hasNumberOfElectrodes
Indicates the relationship that specifies how many electrodes are associated with a given entity.
-
B.
hasElectrode
Indicates that one entity is equipped with, contains, or is associated with an electrode component.
-
C.
hasKochelNumber
Indicates that a musical work is associated with a specific Köchel catalogue number used to uniquely identify compositions by Mozart.
-
D.
hasHereditaryNumber
Indicates that an entity is associated with a specific hereditary identifier or sequence number passed down through a lineage or inheritance chain.
-
E.
hasNumberInSomeSources
Indicates that certain sources report or associate a particular number with the given entity or relation.
- F. None of above. chosen
Provenance (4 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_69f6b5818be881909a32aef194f49c2a |
completed | May 3, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:24 a.m.