Triple
T10957483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifty-Four Forty or Fight |
E258882
|
entity |
| Predicate | demandsBoundaryAtLatitude |
P96828
|
FINISHED |
| Object | 54°40′ north |
—
|
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: 54°40′ north | Statement: [Fifty-Four Forty or Fight, demandsBoundaryAtLatitude, 54°40′ north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demandsBoundaryAtLatitude Context triple: [Fifty-Four Forty or Fight, demandsBoundaryAtLatitude, 54°40′ north]
-
A.
liesWithinLatitudeBand
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
B.
visibleFromLatitudeNorth
Indicates that something can be seen or observed from locations at or north of a specified latitude.
-
C.
visibleFromLatitudeSouth
Indicates that something can be seen or observed from locations situated at or south of a specified latitude.
-
D.
notVisibleFromLatitudesNorthOf
Indicates that the subject cannot be seen or observed from any location situated at latitudes north of the specified reference latitude.
-
E.
isBestSeenFromLatitudes
Indicates that something is most optimally or clearly observable when viewed from specific geographic latitudes.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771260e9881909401a7a7466e1b8a |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.