Triple
T29019765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holozoa |
E737418
|
entity |
| Predicate | containsMulticellularLineages |
P82836
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Holozoa, containsMulticellularLineages, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMulticellularLineages Context triple: [Holozoa, containsMulticellularLineages, true]
-
A.
includesMulticellularLineages
chosen
Indicates that the subject encompasses or contains one or more lineages composed of multicellular organisms.
-
B.
includesUnicellularLineages
Indicates that the subject group or taxon contains one or more lineages that are composed of unicellular organisms.
-
C.
isMulticellular
Indicates that an organism consists of multiple cells organized into a single functional individual.
-
D.
hasNotableLineage
Indicates that an entity descends from, or is associated with, a distinguished or historically significant family, ancestry, or heritage.
-
E.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 28, 2026, 9:48 a.m.