Triple
T9524669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewy bodies |
E229729
|
entity |
| Predicate | locatedInCellularRegion |
P68661
|
FINISHED |
| Object | neuronal cytoplasm |
—
|
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: neuronal cytoplasm | Statement: [Lewy bodies, locatedInCellularRegion, neuronal cytoplasm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCellularRegion Context triple: [Lewy bodies, locatedInCellularRegion, neuronal cytoplasm]
-
A.
cellularLocation
chosen
Indicates the location or compartment within a cell where an entity (such as a molecule or process) is situated or occurs.
-
B.
hasCellularComponent
Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
-
C.
networkRegion
Indicates that an entity belongs to, operates within, or is associated with a specific network-defined geographic or logical region.
-
D.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
E.
hasCellService
Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9899f99481908d374528716027f8 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:59 p.m.