Triple
T8255785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tubulidentata |
E193066
|
entity |
| Predicate | hasDentalStructure |
P35359
|
FINISHED |
| Object | teeth composed of many hexagonal prisms |
—
|
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: teeth composed of many hexagonal prisms | Statement: [Tubulidentata, hasDentalStructure, teeth composed of many hexagonal prisms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDentalStructure Context triple: [Tubulidentata, hasDentalStructure, teeth composed of many hexagonal prisms]
-
A.
hasTeeth
Indicates that one entity possesses teeth as a physical feature.
-
B.
hasMandibles
Indicates that an entity possesses mandibles, i.e., jaw-like mouthparts used for biting, cutting, or holding.
-
C.
hasPharyngealSlits
Indicates that an organism possesses pharyngeal slits, openings in the pharynx that connect the throat to the external environment or a cavity, typically used for filter-feeding or respiration.
-
D.
hasBaleen
Indicates that one entity possesses baleen structures used for filter-feeding.
-
E.
dentition
chosen
Indicates the type, arrangement, or condition of teeth that an entity possesses.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78f9f680819088f1d56e0f98974f |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.