Triple
T25949183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wraith |
E653923
|
entity |
| Predicate | hasBiology |
P73953
|
FINISHED |
| Object | part-Iratus bug |
—
|
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: part-Iratus bug | Statement: [Wraith, hasBiology, part-Iratus bug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiology Context triple: [Wraith, hasBiology, part-Iratus bug]
-
A.
hasBiologicalBasisIn
Indicates that one entity is grounded in, caused by, or dependent on the biological properties, processes, or mechanisms of another entity.
-
B.
hasBiologicalComponents
chosen
Indicates that an entity is composed of, contains, or is associated with one or more biological parts or substances.
-
C.
hasBiologicalKingdom
Indicates that a biological organism is classified as belonging to a particular kingdom in the taxonomic hierarchy.
-
D.
hasBiologicalRelevance
Indicates that something is pertinent to, affects, or is meaningfully connected with biological processes, systems, or functions.
-
E.
usedInBiology
Indicates that something is employed, applied, or serves a function within the field or practices of biology.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 22, 2026, 8:43 a.m.