Triple
T24176863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimrod Expedition |
E599305
|
entity |
| Predicate | reachedFarthestSouthLatitude |
P70550
|
FINISHED |
| Object | 88°23′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: 88°23′S | Statement: [Nimrod Expedition, reachedFarthestSouthLatitude, 88°23′S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedFarthestSouthLatitude Context triple: [Nimrod Expedition, reachedFarthestSouthLatitude, 88°23′S]
-
A.
isSouthernmostLatitudeWhereSunCanBeOverhead
Indicates the southernmost latitude on Earth at which the Sun can appear directly overhead (at the zenith) at some time during the year.
-
B.
lowestLatitude
Indicates that one entity has a latitude value that is lower (i.e., farther south) than another entity or than all others in a given set.
-
C.
southernmost
chosen
Indicates that one entity is located farther to the south than all other comparable entities in a given set or context.
-
D.
northernmostPoint
Indicates the location that lies furthest to the north within the spatial extent of a given entity.
-
E.
isSouthernmostStarOf
Indicates that one star occupies the southernmost position within a specified group, region, or configuration of stars.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.