Triple
T30179688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumerian calendar |
E767166
|
entity |
| Predicate | hasTimeUnit |
P156885
|
FINISHED |
| Object | day |
—
|
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: day | Statement: [Sumerian calendar, hasTimeUnit, day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeUnit Context triple: [Sumerian calendar, hasTimeUnit, day]
-
A.
hasTimeComponent
Indicates that something includes, is associated with, or is characterized by a specific temporal aspect or time-related element.
-
B.
timeUnitOf
chosen
Indicates that one entity specifies the unit of time (e.g., seconds, minutes, hours) in which the other entity’s temporal quantity or duration is expressed.
-
C.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
D.
hasDayUnit
Indicates that something is measured, expressed, or quantified in units of days.
-
E.
hasTimeDimension
Indicates that something possesses or is associated with a temporal aspect, such as duration, point in time, or time-based variation.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 7:26 p.m.