Triple
T5534080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman calendar |
E145116
|
entity |
| Predicate | hadIrregularMonthLengths |
P64771
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Roman calendar, hadIrregularMonthLengths, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadIrregularMonthLengths Context triple: [Roman calendar, hadIrregularMonthLengths, true]
-
A.
hasAverageMonthLength
Indicates that an entity is associated with a specified average length of a month, typically expressed in days.
-
B.
hasAverageYearLength
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
C.
hasVariableMonth
Indicates that something is associated with or occurs in a month that can change rather than being fixed.
-
D.
meetsIrregularly
Indicates that two or more entities come together or interact on a non-fixed, inconsistent, or unpredictable schedule.
-
E.
hasNumberOfDaysIn13thMonth
Indicates the specific count of days that occur in the thirteenth month of a given calendar or time system.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fa0141c81909a216be9f48d64e1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:34 p.m.