Triple
T21483698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planorbidae |
E530060
|
entity |
| Predicate | respiratoryOrgan |
P111616
|
FINISHED |
| Object | pulmonate lung |
—
|
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: pulmonate lung | Statement: [Planorbidae, respiratoryOrgan, pulmonate lung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: respiratoryOrgan Context triple: [Planorbidae, respiratoryOrgan, pulmonate lung]
-
A.
hasRespiratorySystem
Indicates that an entity possesses a respiratory system, i.e., anatomical structures enabling breathing and gas exchange.
-
B.
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).
-
C.
hasOrganSystem
Indicates that an entity possesses or is associated with a particular organ system as part of its biological structure or function.
-
D.
respiration
Indicates the biological process by which an organism exchanges gases with its environment and converts nutrients into usable energy.
-
E.
tipoDeÓrgano
chosen
Indicates that one entity is classified as a specific type or category of organ in relation to another entity.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea35945481909e5982429962de39 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:21 p.m.