Triple
T29856310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan lunar calendar |
E758196
|
entity |
| Predicate | usesRepeatedDays |
P173268
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tibetan lunar calendar, usesRepeatedDays, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRepeatedDays Context triple: [Tibetan lunar calendar, usesRepeatedDays, yes]
-
A.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
B.
usesRepetition
Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
-
C.
isMultiDay
Indicates that the related event, activity, or condition spans more than one calendar day.
-
D.
definesRecurrenceFor
Indicates that one entity specifies or establishes the recurrence pattern or schedule that applies to another entity.
-
E.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 29, 2026, 5:46 p.m.