Triple
T4154187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Winnipeg |
E89976
|
entity |
| Predicate | ianaZoneNameFormat |
P719
|
FINISHED |
| Object | Area/Location |
—
|
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: Area/Location | Statement: [America/Winnipeg, ianaZoneNameFormat, Area/Location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ianaZoneNameFormat Context triple: [America/Winnipeg, ianaZoneNameFormat, Area/Location]
-
A.
timeZoneDatabaseFormat
Indicates that the relationship specifies the time zone using a standardized database format (such as the IANA/Olson time zone identifier).
-
B.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
-
C.
followsIANAZone
Indicates that one entity adopts or conforms to the time zone definition specified by the corresponding IANA time zone identifier of another entity.
-
D.
IANATimeZoneIdentifierExample
chosen
Indicates that the relationship provides an example of an IANA time zone identifier corresponding to a given time zone or context.
-
E.
exampleZoneName
Indicates that an entity is associated with a zone identified by a specific example or placeholder name.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.