Triple
T37450218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buchnera |
E930652
|
entity |
| Predicate | coSpeciationWith |
P87600
|
FINISHED |
| Object | aphids |
—
|
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: aphids | Statement: [Buchnera, coSpeciationWith, aphids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coSpeciationWith Context triple: [Buchnera, coSpeciationWith, aphids]
-
A.
evolvedWith
chosen
Indicates that two or more entities have undergone evolutionary change in mutual influence or parallel over time.
-
B.
speciesConcept
Indicates a conceptual or taxonomic relationship in which an entity is classified as a particular biological species or is associated with a specific species definition.
-
C.
geneticSpecies
Indicates that two entities share the same biological species based on their genetic characteristics.
-
D.
evolutionaryEvent
Indicates an evolutionary change or transition that occurs in a lineage, such as the emergence, modification, or loss of biological traits or taxa over time.
-
E.
laterSpecies
Indicates that one species appears or evolves later in time relative to another species.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.