Triple
T28483089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mani Rimdu festival |
E720746
|
entity |
| Predicate | linkedToCalendar |
P126215
|
FINISHED |
| Object | Tibetan lunar calendar |
—
|
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: Tibetan lunar calendar | Statement: [Mani Rimdu festival, linkedToCalendar, Tibetan lunar calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToCalendar Context triple: [Mani Rimdu festival, linkedToCalendar, Tibetan lunar calendar]
-
A.
calendarLinkedTo
Indicates that one calendar is connected or synchronized with another calendar or calendaring system so that events or updates can be shared or reflected between them.
-
B.
calendarTypeLinked
Indicates that one calendar type is associated or connected to another, typically implying a defined relationship or dependency between the two calendar systems.
-
C.
includedCalendarApp
Indicates that a calendar application is bundled or provided as part of a larger product, service, or system.
-
D.
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).
-
E.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 2:56 a.m.