Triple
T18021051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purkinje fibers |
E431116
|
entity |
| Predicate | histologyFeature |
P40326
|
FINISHED |
| Object | located beneath endocardium |
—
|
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: located beneath endocardium | Statement: [Purkinje fibers, histologyFeature, located beneath endocardium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: histologyFeature Context triple: [Purkinje fibers, histologyFeature, located beneath endocardium]
-
A.
pathologyFeature
Indicates that one entity is a pathological characteristic, sign, or abnormal finding associated with another entity in a medical or biological context.
-
B.
cellBiologyFeature
Indicates a relationship where a biological entity possesses or is characterized by a specific cellular-level property, structure, or function.
-
C.
genomeCharacteristic
Indicates that an entity has a specific property, feature, or attribute related to its genome.
-
D.
anatomicalFeature
Indicates that one entity is an anatomical part, structure, or feature of another entity.
-
E.
biologicalCharacteristic
chosen
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c299c48190b0cceecf77cb6de9 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.