Triple
T29154782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reactome pathways |
E739006
|
entity |
| Predicate | visualizedWith |
P77199
|
FINISHED |
| Object | Pathway Browser |
—
|
NE NERFINISHED |
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: Pathway Browser | Statement: [Reactome pathways, visualizedWith, Pathway Browser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualizedWith Context triple: [Reactome pathways, visualizedWith, Pathway Browser]
-
A.
visualizedIn
chosen
Indicates that something is represented or depicted within a particular visual medium, view, or visualization.
-
B.
visualizationMethod
Indicates the technique or approach used to visually represent data, information, or concepts.
-
C.
visualizationLibrary
Indicates that an entity uses, depends on, or is implemented with a particular visualization library for rendering or displaying visual data.
-
D.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
-
E.
visualElements
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 11:44 a.m.