Triple
T6561299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calendar Round |
E153787
|
entity |
| Predicate | hasSolarCalendarLength |
P71812
|
FINISHED |
| Object | 365 days |
—
|
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: 365 days | Statement: [Calendar Round, hasSolarCalendarLength, 365 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSolarCalendarLength Context triple: [Calendar Round, hasSolarCalendarLength, 365 days]
-
A.
hasSolarDayLength
Indicates that an entity is associated with a specific duration for one complete solar day (the time between successive noons).
-
B.
hasSolarCycle_length_years
Indicates the duration of an entity’s solar activity cycle measured in years.
-
C.
isLunisolar
Indicates that something is based on or determined by both the cycles of the moon and the sun.
-
D.
hasAverageMonthLength
Indicates that an entity is associated with a specified average length of a month, typically expressed in days.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c1b007148190b5164d6d09584cdf |
completed | March 27, 2026, 5:43 p.m. |
Created at: March 27, 2026, 1:52 p.m.