Triple
T3655377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Sentinel Island |
E77515
|
entity |
| Predicate | exclusionZoneRadius |
P20822
|
FINISHED |
| Object | 5 nautical miles |
—
|
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: 5 nautical miles | Statement: [North Sentinel Island, exclusionZoneRadius, 5 nautical miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exclusionZoneRadius Context triple: [North Sentinel Island, exclusionZoneRadius, 5 nautical miles]
-
A.
excludesRegion
Indicates that one entity explicitly omits, leaves out, or does not apply to a specified region or geographic area.
-
B.
excludeRange
Indicates that certain values, items, or elements falling within a specified range are to be omitted or not considered.
-
C.
ringRadius
chosen
Indicates the size of a ring by specifying the distance from its center to its outer edge.
-
D.
hasEvacuationZone
Indicates that a specified area or location falls within a designated evacuation zone associated with another entity (such as an event, hazard, or authority).
-
E.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3baf57c8190b72b5d1b910d9db6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.