Triple
T17086526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cephalaspidomorphi (sensu lato) |
E414612
|
entity |
| Predicate | hasRespiratoryFeature |
P31173
|
FINISHED |
| Object | gill pouches |
—
|
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: gill pouches | Statement: [Cephalaspidomorphi (sensu lato), hasRespiratoryFeature, gill pouches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRespiratoryFeature Context triple: [Cephalaspidomorphi (sensu lato), hasRespiratoryFeature, gill pouches]
-
A.
hasRespiratorySystem
Indicates that an entity possesses a respiratory system, i.e., anatomical structures enabling breathing and gas exchange.
-
B.
mayHaveAccessoryRespiration
Indicates that an entity can exhibit or be associated with an additional or auxiliary form of respiration beyond its primary respiratory process.
-
C.
hasPhysicalFeature
chosen
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
D.
breathes
Indicates that one entity inhales and exhales air or another gas as part of a respiratory process.
-
E.
breathingBehavior
Indicates how an entity performs the act of breathing, such as its pattern, rate, or style of respiration.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe7ccb48190b8fb39e2a0ba0782 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.