Triple
T32494005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agulhas Return Current |
E830466
|
entity |
| Predicate | approximateStartLongitude |
P142874
|
FINISHED |
| Object | around 20°E–25°E |
—
|
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: around 20°E–25°E | Statement: [Agulhas Return Current, approximateStartLongitude, around 20°E–25°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateStartLongitude Context triple: [Agulhas Return Current, approximateStartLongitude, around 20°E–25°E]
-
A.
intendedLongitude
Indicates the longitude value that an entity is meant or planned to have or reach, rather than its actual current longitude.
-
B.
longitudAproximada
Indicates an approximate measurement of the length of something, rather than its exact value.
-
C.
longitudeOfFormationApprox
chosen
Indicates an approximate longitudinal position where a formation or event originated or took shape.
-
D.
landingLatitudeApprox
Indicates an approximate geographic latitude at which a landing event occurs.
-
E.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 1, 2026, 12:59 a.m.