Triple
T29108182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KEGG pathways |
E736820
|
entity |
| Predicate | hasSubCollection |
P64459
|
FINISHED |
| Object | KEGG metabolic pathways |
—
|
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: KEGG metabolic pathways | Statement: [KEGG pathways, hasSubCollection, KEGG metabolic pathways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubCollection Context triple: [KEGG pathways, hasSubCollection, KEGG metabolic pathways]
-
A.
hasSubcollection
chosen
Indicates that one collection contains another collection as a subordinate or nested part of it.
-
B.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
C.
hasAdditionalCollection
Indicates that one entity possesses or is associated with an extra or supplementary collection beyond its primary collection.
-
D.
hasCollectionAt
Indicates that a collection or gathering of items, data, or resources is located, stored, or maintained at a specific place or context.
-
E.
hasSubset
Indicates that one set is entirely contained within another set, with all elements of the first set also belonging to the second.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 28, 2026, 11:16 a.m.