Triple
T9005197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equatorial Undercurrent |
E215125
|
entity |
| Predicate | velocityRange |
P13474
|
FINISHED |
| Object | up to about 1–2 m/s in its core |
—
|
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: up to about 1–2 m/s in its core | Statement: [Equatorial Undercurrent, velocityRange, up to about 1–2 m/s in its core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: velocityRange Context triple: [Equatorial Undercurrent, velocityRange, up to about 1–2 m/s in its core]
-
A.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
B.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
-
D.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
-
E.
displacementRange
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc695afa34819086cf6fcce2997b5f |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.