Triple
T7518896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Strait |
E177715
|
entity |
| Predicate | hasCoordinatesRegion |
P16190
|
FINISHED |
| Object | around 62°S 59°W |
—
|
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 62°S 59°W | Statement: [English Strait, hasCoordinatesRegion, around 62°S 59°W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoordinatesRegion Context triple: [English Strait, hasCoordinatesRegion, around 62°S 59°W]
-
A.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
B.
coordinateRegion
chosen
Indicates that one region is geographically or spatially aligned with, or corresponds to, another region within a shared coordinate framework.
-
C.
hasCoordinatesType
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
-
D.
hasCoordinateRole
Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5f850c081909e697219071293fc |
completed | March 27, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.