Triple
T3018849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosidae |
E82404
|
entity |
| Predicate | includesTaxaWith |
P45064
|
FINISHED |
| Object | nitrogen-fixing symbioses in some lineages |
—
|
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: nitrogen-fixing symbioses in some lineages | Statement: [Rosidae, includesTaxaWith, nitrogen-fixing symbioses in some lineages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTaxaWith Context triple: [Rosidae, includesTaxaWith, nitrogen-fixing symbioses in some lineages]
-
A.
includesExampleTaxon
Indicates that a taxonomic group or concept contains a specific taxon used as an illustrative or representative example.
-
B.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
C.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
-
D.
hasSubtaxon
Indicates that one taxonomic group is a subordinate or included taxon within another taxonomic group.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
- F. None of above. chosen
Provenance (4 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a927b608190ba1392498507b237 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3 p.m.