Triple
T27751112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annapurna glaciers |
E701214
|
entity |
| Predicate | feed |
P9008
|
FINISHED |
| Object | major river systems of central Nepal |
—
|
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: major river systems of central Nepal | Statement: [Annapurna glaciers, feed, major river systems of central Nepal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feed Context triple: [Annapurna glaciers, feed, major river systems of central Nepal]
-
A.
feedSystem
chosen
Indicates that one entity supplies or provides input, resources, or data into another entity or system for its operation or processing.
-
B.
feedsOn
Indicates that one entity obtains nourishment by consuming another entity as food.
-
C.
feedsAt
Indicates that one entity obtains or consumes food at, from, or using another entity (such as a location, source, or feeding apparatus).
-
D.
feedsAccelerator
Indicates that one entity supplies or directs input, resources, or power into an accelerator system for its operation.
-
E.
feedsDraft
Indicates that one entity provides or supplies a draft version of something 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6371efb248190a2e1c41e07271489 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:20 p.m.