Triple
T29019770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holozoa |
E737418
|
entity |
| Predicate | hasGenomicStudies |
P94165
|
FINISHED |
| Object | extensive |
—
|
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: extensive | Statement: [Holozoa, hasGenomicStudies, extensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenomicStudies Context triple: [Holozoa, hasGenomicStudies, extensive]
-
A.
hasGenealogicalStudy
Indicates that a subject is associated with or documented in a genealogical study examining familial or ancestral relationships.
-
B.
hasScientificStudy
Indicates that there exists a scientific study that investigates, analyzes, or provides evidence about the referenced entity or relationship.
-
C.
hasGeneticEvidence
Indicates that there is genetic data or analysis supporting the existence, validity, or nature of the specified relationship or association between entities.
-
D.
geneticStudySubject
chosen
Indicates that an entity is the subject or focus of a genetic study or genetic analysis.
-
E.
hasStudyModel
Indicates that an entity is associated with, or defined by, a particular study model used for analysis, simulation, or representation.
- 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_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 9:48 a.m.