Triple
T37450221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buchnera |
E930652
|
entity |
| Predicate | cellLocationInHost |
P187838
|
FINISHED |
| Object | cytoplasm of specialized aphid cells |
—
|
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: cytoplasm of specialized aphid cells | Statement: [Buchnera, cellLocationInHost, cytoplasm of specialized aphid cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellLocationInHost Context triple: [Buchnera, cellLocationInHost, cytoplasm of specialized aphid cells]
-
A.
cellularLocation
Indicates the location or compartment within a cell where an entity (such as a molecule or process) is situated or occurs.
-
B.
cellBodiesLocatedIn
Indicates that the cell bodies of a group of cells are situated within a specified anatomical region or structure.
-
C.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
D.
hostLatticeFor
Indicates that one entity serves as the structural lattice framework within which another entity is incorporated, embedded, or accommodated.
-
E.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
- 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_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. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.