Triple
T4944364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solemnity |
E111009
|
entity |
| Predicate | calendarClassification |
P87
|
FINISHED |
| Object | universal solemnity |
—
|
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: universal solemnity | Statement: [Solemnity, calendarClassification, universal solemnity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarClassification Context triple: [Solemnity, calendarClassification, universal solemnity]
-
A.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
B.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
C.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
D.
classificationChange
Indicates a change in the category, type, or status under which an entity is classified.
-
E.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a8e5388190882831d7828441d3 |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.