Triple
T18602772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enteropneusta |
E454657
|
entity |
| Predicate | hasHeart |
P16677
|
FINISHED |
| Object | dorsal contractile vessel |
—
|
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: dorsal contractile vessel | Statement: [Enteropneusta, hasHeart, dorsal contractile vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeart Context triple: [Enteropneusta, hasHeart, dorsal contractile vessel]
-
A.
isHeartOf
Indicates that one entity functions as the central, most vital or defining core of another entity.
-
B.
heartPresence
chosen
Indicates the existence or presence of a heart in or associated with the referenced entity.
-
C.
heartColor
Indicates the color attribute associated with a heart.
-
D.
heartSymbol2
Indicates a relationship where one entity expresses affection, love, or strong positive emotion toward another, often symbolized by a heart icon or shape.
-
E.
heartShape
Indicates that one entity has a heart-like or heart-shaped form in relation to another entity or context.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54751d7ec81909efc4867f649002e |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.