Triple
T29154789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reactome pathways |
E739006
|
entity |
| Predicate | crossReferencedWith |
P111150
|
FINISHED |
| Object | KEGG pathways |
—
|
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: KEGG pathways | Statement: [Reactome pathways, crossReferencedWith, KEGG pathways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossReferencedWith Context triple: [Reactome pathways, crossReferencedWith, KEGG pathways]
-
A.
crossReference
chosen
Indicates that one entity refers the user to another related entity or source for additional or supporting information.
-
B.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
C.
metaReferenceOf
Indicates that one entity serves as a meta-level reference or description of another entity, rather than being the primary object itself.
-
D.
crossedWith
Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
-
E.
crossesAssociatedWith
Indicates a relationship where one entity’s crossing or intersection is functionally or contextually linked to 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_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 11:44 a.m.