Triple
T15903022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagaung |
E385635
|
entity |
| Predicate | hasLunisolarProperty |
P71361
|
FINISHED |
| Object | based on both lunar phases and solar year |
—
|
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: based on both lunar phases and solar year | Statement: [Wagaung, hasLunisolarProperty, based on both lunar phases and solar year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLunisolarProperty Context triple: [Wagaung, hasLunisolarProperty, based on both lunar phases and solar year]
-
A.
isLunisolar
chosen
Indicates that something is based on or determined by both the cycles of the moon and the sun.
-
B.
hasLunarPhaseStart
Indicates that an entity (such as a lunar phase event) has a specific starting time or point at which that lunar phase begins.
-
C.
hasLunarBasis
Indicates that something is founded on, derived from, or fundamentally based on the Moon or lunar characteristics.
-
D.
lunarCalendar
Indicates that the referenced system, event, or date is defined, measured, or scheduled according to a calendar based on the phases or cycles of the Moon.
-
E.
hasSolarCalendarLength
Indicates that an entity’s solar calendar is characterized by a specific duration or number of 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:52 a.m.