Triple
T3012447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Dependency |
E82252
|
entity |
| Predicate | longitudeExtent |
P23540
|
FINISHED |
| Object | between 160°E and 150°W (approximate) |
—
|
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: between 160°E and 150°W (approximate) | Statement: [Ross Dependency, longitudeExtent, between 160°E and 150°W (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longitudeExtent Context triple: [Ross Dependency, longitudeExtent, between 160°E and 150°W (approximate)]
-
A.
regionLongitudeRange
chosen
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
B.
maximumExtent
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
-
C.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
D.
peakTerritorialExtent
Indicates the maximum geographic area or territorial size that an entity controlled or occupied at the height of its expansion.
-
E.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a66c334819082d1d320c48eca1b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.