Triple
T22661987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuber |
E559687
|
entity |
| Predicate | isEctomycorrhizal |
P66798
|
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: [Tuber, isEctomycorrhizal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEctomycorrhizal Context triple: [Tuber, isEctomycorrhizal, true]
-
A.
isActinorhizalPlant
Indicates that a plant forms a symbiotic, nitrogen-fixing association with actinorhizal (Frankia) bacteria in its roots.
-
B.
hasTeleomorph
Indicates a relationship where one organism or taxon has a corresponding sexual (teleomorphic) form in its life cycle or classification.
-
C.
isLargestFungalPhylum
Indicates that the subject phylum is the largest among all fungal phyla, typically in terms of number of species.
-
D.
rhizoidType
Indicates the specific kind or category of rhizoid structure associated with an organism or anatomical feature.
-
E.
formsMycorrhizaWith
chosen
Indicates that one organism forms a mutualistic mycorrhizal association with another organism, typically between a fungus and a plant root system.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765fe7d081908087778c54c1e612 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.