Triple
T38297282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romans d'Isonzo |
E1032123
|
entity |
| Predicate | locatedInSummerTimeZoneRegion |
P5550
|
FINISHED |
| Object | UTC+2 |
—
|
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: UTC+2 | Statement: [Romans d'Isonzo, locatedInSummerTimeZoneRegion, UTC+2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSummerTimeZoneRegion Context triple: [Romans d'Isonzo, locatedInSummerTimeZoneRegion, UTC+2]
-
A.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
B.
summerTimeZone
chosen
Indicates that a specified region or entity uses a particular time zone during the summer or daylight-saving period.
-
C.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
D.
locatedInUtmZone
Indicates that something is situated within a specific Universal Transverse Mercator (UTM) coordinate zone.
-
E.
hasTimeZoneInWinter
Indicates that an entity is associated with a specific time zone during the winter season.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.