Triple
T2276671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Pilgrimage Festivals |
E50785
|
entity |
| Predicate | calendarPosition |
P29012
|
FINISHED |
| Object | spring and autumn |
—
|
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: spring and autumn | Statement: [Three Pilgrimage Festivals, calendarPosition, spring and autumn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarPosition Context triple: [Three Pilgrimage Festivals, calendarPosition, spring and autumn]
-
A.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
-
B.
positionInGregorianCalendar
chosen
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
C.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
-
D.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
E.
calendarFunction
Indicates a relationship where an entity serves as a function or operation within a calendar system, such as computing or manipulating dates, times, or calendar-related events.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1ecc600819095dd4f69af1d18d8 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.