Triple
T13692647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tropical Indian Ocean |
E328306
|
entity |
| Predicate | hasLongitudeRange |
P23540
|
FINISHED |
| Object | approximately 40°E to 120°E |
—
|
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: approximately 40°E to 120°E | Statement: [tropical Indian Ocean, hasLongitudeRange, approximately 40°E to 120°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongitudeRange Context triple: [tropical Indian Ocean, hasLongitudeRange, approximately 40°E to 120°E]
-
A.
regionLongitudeRange
chosen
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
B.
liesWithinLatitudeBand
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
C.
demandsBoundaryAtLatitude
Indicates that an entity asserts or requires that a boundary be established along a specific line of latitude.
-
D.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
E.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum range.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8757b648190a26181efbad09a43 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.