Triple
T16050213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | proleptic Gregorian calendar |
E389332
|
entity |
| Predicate | hasEpochRelation |
P21934
|
FINISHED |
| Object | can be mapped to Julian day numbers |
—
|
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: can be mapped to Julian day numbers | Statement: [proleptic Gregorian calendar, hasEpochRelation, can be mapped to Julian day numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpochRelation Context triple: [proleptic Gregorian calendar, hasEpochRelation, can be mapped to Julian day numbers]
-
A.
hasChronologyRelation
Indicates a temporal ordering relationship between entities, specifying how one relates to another in time (e.g., before, after, or overlapping).
-
B.
isEpochBoundaryFor
Indicates that something marks or defines the transition point between two distinct epochs for another entity.
-
C.
epochReference
chosen
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
D.
hasTemporalAttribute
Indicates that an entity is associated with a specific temporal property or characteristic, such as time, duration, or period.
-
E.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.