Triple
T14812887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llewellyn Glacier |
E348229
|
entity |
| Predicate | hasMovementDirection |
P16306
|
FINISHED |
| Object | generally southward toward Atlin Lake |
—
|
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: generally southward toward Atlin Lake | Statement: [Llewellyn Glacier, hasMovementDirection, generally southward toward Atlin Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementDirection Context triple: [Llewellyn Glacier, hasMovementDirection, generally southward toward Atlin Lake]
-
A.
movementDirection
chosen
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
B.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
C.
hasKeyMovement
Indicates that one entity possesses or defines the primary or characteristic movement pattern associated with another entity.
-
D.
hasMovementVariant
Indicates that one movement is an alternative or variant form of another movement.
-
E.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf374f288190aa918b1b6b507420 |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:48 a.m.