Triple
T2704369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmic Calendar |
E59307
|
entity |
| Predicate | midnightJanuary1Represents |
P22624
|
FINISHED |
| Object | moment of the Big Bang |
—
|
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: moment of the Big Bang | Statement: [Cosmic Calendar, midnightJanuary1Represents, moment of the Big Bang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: midnightJanuary1Represents Context triple: [Cosmic Calendar, midnightJanuary1Represents, moment of the Big Bang]
-
A.
midnightSignificance
chosen
Indicates the special meaning, importance, or notable events associated with the time of midnight in a given context.
-
B.
newYearDateGregorian
Indicates the specific calendar date on which New Year’s Day occurs according to the Gregorian calendar.
-
C.
commandedAsFirstMonthIn
Indicates that an entity is designated or ordered to serve as the first month within a specified temporal system or context.
-
D.
newYearDateGregorianLeapOverlap
Indicates that the Gregorian calendar New Year’s date coincides or overlaps with a date defined for leap-year-related observances or calculations.
-
E.
monthObserved
Indicates the month during which an event, observation, or measurement took place.
- 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.