Triple
T18021061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purkinje fibers |
E431116
|
entity |
| Predicate | speciesPresentIn |
P91995
|
FINISHED |
| Object | humans |
—
|
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: humans | Statement: [Purkinje fibers, speciesPresentIn, humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesPresentIn Context triple: [Purkinje fibers, speciesPresentIn, humans]
-
A.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
B.
foundInSpecies
chosen
Indicates that something (such as a feature, gene, or characteristic) occurs in, is present in, or is observed within a particular species.
-
C.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
D.
speciesHome
Indicates that a particular location serves as the natural habitat or primary living environment for a given species.
-
E.
someSpeciesAre
Indicates that at least one member of a specified group or category belongs to, or can be classified as, a particular species.
- 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.