Triple
T34746883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitrastemonaceae |
E1001660
|
entity |
| Predicate | isHoloparasitic |
P168448
|
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: [Mitrastemonaceae, isHoloparasitic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHoloparasitic Context triple: [Mitrastemonaceae, isHoloparasitic, true]
-
A.
parasitizes
Indicates a relationship in which one organism lives on or in another organism, deriving nutrients or benefits at the host’s expense.
-
B.
isSymbiotic
Indicates a mutually dependent relationship in which two entities interact in ways that benefit at least one and typically support the survival or well-being of both.
-
C.
parasiticStage
chosen
Indicates that an organism is in a life-cycle stage during which it lives as a parasite, deriving resources from a host.
-
D.
isNonParasitic
Indicates that the entity does not live as a parasite and does not rely on another organism in a parasitic relationship.
-
E.
hasTeleomorph
Indicates a relationship where one organism or taxon has a corresponding sexual (teleomorphic) form in its life cycle or classification.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.