Triple
T31251038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhenyuan |
E796816
|
entity |
| Predicate | usedInCalendarType |
P97978
|
FINISHED |
| Object | lunisolar 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: lunisolar calendar | Statement: [Zhenyuan, usedInCalendarType, lunisolar calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCalendarType Context triple: [Zhenyuan, usedInCalendarType, lunisolar calendar]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
usedInCalendarSystem
chosen
Indicates that something (such as a time unit, era, or convention) is employed as part of a particular calendar system.
-
C.
usesCalendarEvent
Indicates that one entity makes use of, interacts with, or relies on a specific calendar event.
-
D.
calendarUsedFor
Indicates that a particular calendar is employed or applied for a specific purpose, context, or activity.
-
E.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 29, 2026, 9:11 p.m.