Triple
T8648193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chirikof Point (islet) |
E205031
|
entity |
| Predicate | locatedInUtmZone |
P84122
|
FINISHED |
| Object | UTM zone 3V |
—
|
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: UTM zone 3V | Statement: [Chirikof Point (islet), locatedInUtmZone, UTM zone 3V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInUtmZone Context triple: [Chirikof Point (islet), locatedInUtmZone, UTM zone 3V]
-
A.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
B.
locatedInTimeZoneUTCOffsetDST
Indicates that an entity exists or operates in a time zone that observes daylight saving time with a specified UTC offset during that DST period.
-
C.
partlyLocatedInTimeZone
Indicates that an entity’s extent overlaps multiple time zones, with at least part of it falling within the specified time zone.
-
D.
locatedInTimeZoneDatabaseCountry
Indicates that the entity is situated in, or associated with, a country as defined in the time zone database.
-
E.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4812b7bc8190acb40da57cad293a |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc473e44988190a3b02498e5fff668 |
completed | March 31, 2026, 10:14 p.m. |
Created at: March 30, 2026, 6:29 p.m.