Triple
T8252005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amhara Region |
E192978
|
entity |
| Predicate | usesTimeFormat |
P2162
|
FINISHED |
| Object | Ethiopian time |
—
|
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: Ethiopian time | Statement: [Amhara Region, usesTimeFormat, Ethiopian time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTimeFormat Context triple: [Amhara Region, usesTimeFormat, Ethiopian time]
-
A.
dateFormat
Indicates the specific pattern or structure used to represent a date as a formatted string.
-
B.
timeNotation
chosen
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
C.
usesScheduleFormat
Indicates that one entity adopts or follows the schedule structure, pattern, or formatting defined by another entity.
-
D.
isStandardTime
Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
-
E.
representsTimeIn
Indicates that one entity expresses, encodes, or specifies the time at which another entity occurs, is valid, or is observed.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78ca4b0881909bb1fb550dba59e7 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.