Triple
T8926995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecology |
E212559
|
entity |
| Predicate | levelOfOrganizationCovered |
P29174
|
FINISHED |
| Object | individual organisms |
—
|
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: individual organisms | Statement: [Ecology, levelOfOrganizationCovered, individual organisms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelOfOrganizationCovered Context triple: [Ecology, levelOfOrganizationCovered, individual organisms]
-
A.
hasTissueLevelOrganization
Indicates that an entity possesses a structural organization composed of multiple tissues arranged into functional units.
-
B.
typeOfOrganCovered
Indicates the specific organ or body part that is protected or covered by something (such as a device, garment, or material).
-
C.
coversLevel
chosen
Indicates that one entity includes or encompasses a particular level or layer of another entity or system.
-
D.
hasOrganLevelOrganization
Indicates that an entity possesses a level of biological organization in which distinct organs are present and functionally integrated.
-
E.
governingBodyLevel
Indicates the hierarchical level or tier at which a governing body operates within a political or organizational structure.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6671557c81909f3837ffd6a15ffe |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.