Triple
T30086774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betz cells |
E764621
|
entity |
| Predicate | hasDendriteType |
P194859
|
FINISHED |
| Object | apical dendrite |
—
|
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: apical dendrite | Statement: [Betz cells, hasDendriteType, apical dendrite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDendriteType Context triple: [Betz cells, hasDendriteType, apical dendrite]
-
A.
hasDuneType
Indicates that one entity is characterized by or associated with a specific type or classification of dune.
-
B.
hasDistributionType
Indicates the type or pattern of distribution associated with an entity, specifying how something is spread, allocated, or made available.
-
C.
hasDiscoveryType
Indicates the specific manner, method, or category by which something was discovered.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasTypeOfDescent
Indicates that one entity possesses a particular kind or category of ancestral or lineage-based origin in relation to another entity.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: April 29, 2026, 7:04 p.m.