Triple
T5619953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Weddell |
E147575
|
entity |
| Predicate | reachedLatitude |
P35088
|
FINISHED |
| Object | 74°15′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: 74°15′S | Statement: [James Weddell, reachedLatitude, 74°15′S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedLatitude Context triple: [James Weddell, reachedLatitude, 74°15′S]
-
A.
highestLatitudeReached
chosen
Indicates the maximum latitude that an entity has ever reached during its movement or existence.
-
B.
coordinateLatitude
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
C.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
D.
reasonForLatitude
Indicates that one factor or circumstance serves as the explanation or cause for a particular degree or extent of latitude (freedom, variation, or deviation) in a situation or condition.
-
E.
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.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022108db8819098739510366adee1 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.