Triple
T18454247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Stockholm |
E450861
|
entity |
| Predicate | historicalTimeStandard |
P1832
|
FINISHED |
| Object | CET adopted in early 20th century |
—
|
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: CET adopted in early 20th century | Statement: [Europe/Stockholm, historicalTimeStandard, CET adopted in early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTimeStandard Context triple: [Europe/Stockholm, historicalTimeStandard, CET adopted in early 20th century]
-
A.
previousTimeStandard
Indicates that one time standard directly preceded another in chronological use or official adoption.
-
B.
relatedTimeStandard
Indicates that one time-related entity is defined, interpreted, or aligned according to a particular time standard or reference timescale.
-
C.
timeZoneHistorical
chosen
Indicates that there is a historical time zone relationship, specifying how an entity’s time zone (including offsets, rules, or changes) applied during past periods.
-
D.
timePeriodOfStandardization
Indicates the time span during which a particular standard was formally established or in effect.
-
E.
observedAsStandardTimeIn
Indicates that a particular time standard is used as the official or standard time within a specified place or region.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264b200c8190be2e79ca5ea0b082 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.