Triple
T15725659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sexagenary cycle |
E381210
|
entity |
| Predicate | timeGranularity |
P119939
|
FINISHED |
| Object | year |
—
|
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: year | Statement: [sexagenary cycle, timeGranularity, year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeGranularity Context triple: [sexagenary cycle, timeGranularity, year]
-
A.
timeTravelGranularity
Indicates the level of temporal precision or resolution at which time travel or time-based operations can occur between entities.
-
B.
reservationGranularity
Indicates the level of detail or unit (such as time, quantity, or capacity) at which a reservation can be specified or managed.
-
C.
pricingGranularity
Indicates the level of detail or resolution at which prices are defined, grouped, or applied within a pricing structure or model.
-
D.
timeCharacteristic
Indicates a relationship where one entity specifies a temporal property, feature, or constraint that characterizes another entity or event.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb357a88190a92641c8a8c20573 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.