Triple
T7946970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BJT |
E184520
|
entity |
| Predicate | coversMultipleGeographicalTimeZones |
P3413
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [BJT, coversMultipleGeographicalTimeZones, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversMultipleGeographicalTimeZones Context triple: [BJT, coversMultipleGeographicalTimeZones, yes]
-
A.
hasNumberOfNationalTimeZones
Indicates the quantity of distinct official time zones that a nation or country uses within its territory.
-
B.
hasTimeZones
chosen
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
C.
numberOfTimeZonesCrossed
Indicates the count of distinct time zones that an entity passes through or traverses during a specified journey or process.
-
D.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
E.
observesDaylightSavingTimeInSomeRegions
Indicates that the entity follows daylight saving time practices, but only in certain parts or regions of its jurisdiction or coverage 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.