Triple
T32541421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feriae Latinae |
E831721
|
entity |
| Predicate | calendarStatus |
P126215
|
FINISHED |
| Object | moveable feast |
—
|
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: moveable feast | Statement: [Feriae Latinae, calendarStatus, moveable feast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarStatus Context triple: [Feriae Latinae, calendarStatus, moveable feast]
-
A.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
-
B.
calendarAssociation
chosen
Indicates a relationship where one entity is linked to or associated with a particular calendar or calendaring context (such as events, schedules, or timeframes).
-
C.
calendarVariesBy
Indicates that the characteristics or values of a calendar (such as dates, events, or structure) change depending on another specified factor or context.
-
D.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
E.
eventStatus
Indicates the current state or phase of an event within its lifecycle (e.g., planned, ongoing, completed, or canceled).
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57f14348190a0e2b98597e5ba25 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.