Triple
T16108056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Bahrain |
E390793
|
entity |
| Predicate | uses24HourClockCommonly |
P2162
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Asia/Bahrain, uses24HourClockCommonly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uses24HourClockCommonly Context triple: [Asia/Bahrain, uses24HourClockCommonly, true]
-
A.
timeNotation
chosen
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
B.
usedForCivilTimeIn
Indicates that something (typically a time scale or standard) is used as the basis for keeping official civil time within a specified region or jurisdiction.
-
C.
isStandardTime
Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
-
D.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
-
E.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20165aa9c81908c5358cca2b0d0fe |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.