Triple
T2704362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmic Calendar |
E59307
|
entity |
| Predicate | compressesTimeSpan |
P9981
|
FINISHED |
| Object | 13.8 billion years into one 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: 13.8 billion years into one year | Statement: [Cosmic Calendar, compressesTimeSpan, 13.8 billion years into one year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compressesTimeSpan Context triple: [Cosmic Calendar, compressesTimeSpan, 13.8 billion years into one year]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
C.
timescale
chosen
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda518c58819096c8b67c0f754655 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.