Triple
T3091719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madden–Julian Oscillation |
E64496
|
entity |
| Predicate | propagationDirection |
P30196
|
FINISHED |
| Object | eastward |
—
|
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: eastward | Statement: [Madden–Julian Oscillation, propagationDirection, eastward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propagationDirection Context triple: [Madden–Julian Oscillation, propagationDirection, eastward]
-
A.
propagationMethod
Indicates the means or mechanism by which something spreads, reproduces, or is transmitted from one entity or location to another.
-
B.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
C.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
-
D.
directionalConfiguration
Indicates a specific spatial or directional arrangement that one entity has relative to another.
-
E.
hasDirectionType
chosen
Indicates that something possesses or is associated with a specific type or category of direction.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada20eeee88190a5eecfce10e3848c |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.