Triple
T18137270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subantarctic Mode Water |
E434168
|
entity |
| Predicate | extendsLatitude |
P130596
|
FINISHED |
| Object | roughly 30°S–50°S |
—
|
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: roughly 30°S–50°S | Statement: [Subantarctic Mode Water, extendsLatitude, roughly 30°S–50°S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsLatitude Context triple: [Subantarctic Mode Water, extendsLatitude, roughly 30°S–50°S]
-
A.
regionLongitudeRange
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
B.
extendedTowards
Indicates that one entity is stretched or directed outward in the direction of another entity or location.
-
C.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
-
D.
parallelOfLatitude
Indicates that one entity is a line or circle on a sphere (typically Earth) that is at a constant latitude relative to another reference.
-
E.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
- F. None of above. chosen
Provenance (4 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de089f1881908dff9835be5129a1 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:29 a.m.