Triple
T8357394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golgi apparatus |
E196713
|
entity |
| Predicate | typicallyLocatedNear |
P41003
|
FINISHED |
| Object | endoplasmic reticulum |
—
|
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: endoplasmic reticulum | Statement: [Golgi apparatus, typicallyLocatedNear, endoplasmic reticulum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyLocatedNear Context triple: [Golgi apparatus, typicallyLocatedNear, endoplasmic reticulum]
-
A.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
-
B.
situatedNextTo
Indicates that one entity is located immediately beside another, with no significant separation between them.
-
C.
residesNear
chosen
Indicates that one entity lives or is located in close physical proximity to another entity.
-
D.
partlyLocatedNear
Indicates that one entity is situated near another, but only a portion or subset of it lies within that nearby area.
-
E.
locatedInOrAdjacentTo
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804b57f88190907a4e4e389caf5f |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.