Triple
T408748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Pole |
E9439
|
entity |
| Predicate | hasTimeConvention |
P3413
|
FINISHED |
| Object | expeditions choose convenient time zone |
—
|
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: expeditions choose convenient time zone | Statement: [North Pole, hasTimeConvention, expeditions choose convenient time zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeConvention Context triple: [North Pole, hasTimeConvention, expeditions choose convenient time zone]
-
A.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
-
B.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
-
C.
standardTimeCounterpart
Indicates that one time representation is the corresponding value expressed in a standard or canonical time format for the other.
-
D.
hasTimeZones
chosen
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
settlementPattern
Indicates how human dwellings or communities are spatially arranged and distributed across a geographic area.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbf0650819080753815ca280eec |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.