Triple
T3653579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reptilia |
E77476
|
entity |
| Predicate | heartStructure |
P50704
|
FINISHED |
| Object | three-chambered heart in most groups |
—
|
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: three-chambered heart in most groups | Statement: [Reptilia, heartStructure, three-chambered heart in most groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heartStructure Context triple: [Reptilia, heartStructure, three-chambered heart in most groups]
-
A.
heartPresence
Indicates the existence or presence of a heart in or associated with the referenced entity.
-
B.
vascularSystem
Indicates the relationship in which an entity possesses or is associated with a system of blood vessels that transports blood throughout a body.
-
C.
mainOrganOf
Indicates that one entity is the primary or central organ responsible for the core functions of another entity (such as an organism or system).
-
D.
cellStructure
Indicates the structural organization, components, and physical arrangement that make up a cell.
-
E.
hasOrganSystem
Indicates that an entity possesses or is associated with a particular organ system as part of its biological structure or function.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b805a48190a7bc230a382365d6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adbae14d488190a6024548979c6faf |
completed | March 8, 2026, 6:07 p.m. |
Created at: March 8, 2026, 3:24 p.m.