Triple
T29856308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan lunar calendar |
E758196
|
entity |
| Predicate | usesDayCount |
P64465
|
FINISHED |
| Object | lunar days (tshes) |
—
|
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: lunar days (tshes) | Statement: [Tibetan lunar calendar, usesDayCount, lunar days (tshes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDayCount Context triple: [Tibetan lunar calendar, usesDayCount, lunar days (tshes)]
-
A.
hasDayCount
chosen
Indicates that an entity is associated with a specific number of days, expressing the duration or count of days related to it.
-
B.
dayCountDependsOn
Indicates that the number of days for one element is determined or constrained by another element.
-
C.
hasDayCountPattern
Indicates a relationship where something follows or is associated with a specific pattern in the number or arrangement of days.
-
D.
hasDayCountCommonYear
Indicates that something has a specified number of days as it occurs in a common (non-leap) year.
-
E.
hasDays
Indicates that an entity is associated with, spans, or occurs on specific days.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 5:46 p.m.