Triple
T29019810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holomycota |
E737419
|
entity |
| Predicate | containsLineage |
P77522
|
FINISHED |
| Object | filamentous fungi |
—
|
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: filamentous fungi | Statement: [Holomycota, containsLineage, filamentous fungi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLineage Context triple: [Holomycota, containsLineage, filamentous fungi]
-
A.
hasLineageCharacteristic
Indicates that an entity possesses a specific trait, feature, or quality that is inherited or derived from its lineage or ancestral line.
-
B.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
C.
hasLineageName
Indicates that an entity is associated with or identified by a specific lineage name within a genealogical or hierarchical context.
-
D.
hasLineageMember
chosen
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
-
E.
hasLineageStatus
Indicates the lineage or ancestry classification assigned to an entity, such as whether and how it descends from or is derived from another.
- 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_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 28, 2026, 9:48 a.m.