Triple
T21889887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urdoviza Glacier |
E540510
|
entity |
| Predicate | flowsNorth |
P125930
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Urdoviza Glacier, flowsNorth, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsNorth Context triple: [Urdoviza Glacier, flowsNorth, true]
-
A.
flowsNorthFrom
Indicates that something moves or travels in a generally northward direction starting from a specified origin.
-
B.
flowsNorthOf
Indicates that one entity (typically a watercourse or current) moves in a generally northward direction while remaining geographically north of the other entity.
-
C.
flowsNorthward
chosen
Indicates that the subject moves or travels in a generally northward direction relative to a reference frame or location.
-
D.
flowsSouthTo
Indicates that something moves or is directed in a generally southward direction until it reaches or connects with another location or entity.
-
E.
flowsAcross
Indicates that one entity moves or extends in a continuous stream from one side of another entity to the other, traversing its area or boundary.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ef2b648190bbd78f6b3958d2ee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:06 p.m.