Triple
T19518790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Glacier |
E488348
|
entity |
| Predicate | flowsOn |
P136219
|
FINISHED |
| Object | slopes of Mount Olympus |
—
|
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: slopes of Mount Olympus | Statement: [White Glacier, flowsOn, slopes of Mount Olympus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsOn Context triple: [White Glacier, flowsOn, slopes of Mount Olympus]
-
A.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
B.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
C.
flowsTo
Indicates that something moves or is directed from one location or entity toward and into another, typically in a continuous or channel-like manner.
-
D.
flowsOver
Indicates that one substance or medium moves across the surface or boundary of another, covering or passing above it.
-
E.
flowsUnder
Indicates that one entity (typically a river, stream, or liquid) passes beneath another entity (such as a bridge, structure, or obstacle) along its course.
- F. None of above. chosen
Provenance (4 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359edd508190afd68739de676ed7 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7d0da88190aabf8b5799691fb1 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.