Triple
T16542470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Warsaw |
E401852
|
entity |
| Predicate | ianaTimeZoneDatabaseVersionIntroduced |
P123964
|
FINISHED |
| Object | pre-2000 (exact version varies) |
—
|
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: pre-2000 (exact version varies) | Statement: [Europe/Warsaw, ianaTimeZoneDatabaseVersionIntroduced, pre-2000 (exact version varies)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ianaTimeZoneDatabaseVersionIntroduced Context triple: [Europe/Warsaw, ianaTimeZoneDatabaseVersionIntroduced, pre-2000 (exact version varies)]
-
A.
timeZoneDatabaseVersioning
Indicates how versions are assigned, tracked, or managed for entries in a time zone database.
-
B.
ianaTimeZoneId
Indicates the association between an entity and its time zone as identified by a standard IANA time zone identifier (e.g., "America/New_York").
-
C.
timeZoneDatabase
Indicates that there is an association between something (such as a system, service, or region) and a specific time zone database it uses or is defined by.
-
D.
ianaTimeZoneRegion
Indicates that one entity is an IANA time zone region associated with or applicable to another entity.
-
E.
timeZoneDatabaseFormat
Indicates that the relationship specifies the time zone using a standardized database format (such as the IANA/Olson time zone identifier).
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455db6788190b929546050ea2488 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.