Triple
T37308549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Atlantic jet stream |
E926142
|
entity |
| Predicate | canShift |
P159963
|
FINISHED |
| Object | northward |
—
|
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: northward | Statement: [North Atlantic jet stream, canShift, northward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canShift Context triple: [North Atlantic jet stream, canShift, northward]
-
A.
shiftsWhen
Indicates that one state, condition, or configuration changes to another under specified circumstances or triggers.
-
B.
canChangeIn
Indicates that one entity is capable of undergoing alteration, transformation, or variation within the context or influence of another entity or condition.
-
C.
hasDynamicShifts
Indicates that something exhibits changes or transitions in state, intensity, or behavior over time rather than remaining constant.
-
D.
canMove
chosen
Indicates that one entity has the ability or permission to change its location or position relative to its environment or another entity.
-
E.
shiftsThrough
Indicates that one entity moves or passes through another entity or medium, typically involving a change in position or state during the traversal.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.