Triple
T2209019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furious Fifties |
E50869
|
entity |
| Predicate | hasApproximateSouthernBoundary |
P13333
|
FINISHED |
| Object | 60° south latitude |
—
|
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: 60° south latitude | Statement: [Furious Fifties, hasApproximateSouthernBoundary, 60° south latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateSouthernBoundary Context triple: [Furious Fifties, hasApproximateSouthernBoundary, 60° south latitude]
-
A.
southernBoundaryReference
chosen
Indicates that one entity is used as the reference or defining limit for the southern boundary of another entity.
-
B.
isSouthernmostPartOf
Indicates that one entity is the geographically furthest south portion or section of another entity.
-
C.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
D.
northernBoundaryReference
Indicates the feature or element that serves as the reference for defining the northern boundary of something.
-
E.
hasUncertainBoundary
Indicates that the boundary or extent of something is not clearly defined, fixed, or precisely known.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1baa0948190b07ffc347a4f714e |
completed | March 7, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69abbda8a6dc8190aa855ce2d17194b1 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.