Triple
T617236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cephalochordata |
E14432
|
entity |
| Predicate | heartPresence |
P16677
|
FINISHED |
| Object | no true heart |
—
|
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: no true heart | Statement: [Cephalochordata, heartPresence, no true heart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heartPresence Context triple: [Cephalochordata, heartPresence, no true heart]
-
A.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
B.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
-
C.
hasPin
Indicates that one entity possesses, includes, or is equipped with a specific pin (such as a connector pin, security PIN, or fastening pin).
-
D.
hasPlaque
Indicates that an entity possesses or displays a plaque, such as a commemorative plate or a deposit on a surface.
-
E.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e2418c881908552d2c4a5006e97 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49d76062c819083ac33f1f87097c7 |
completed | March 1, 2026, 8:11 p.m. |
Created at: March 1, 2026, 7:35 p.m.