Triple
T38136050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xīnhài Gémìng |
E952352
|
entity |
| Predicate | hasCalendarReference |
P197024
|
FINISHED |
| Object | Xinhai year of the sexagenary cycle |
—
|
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: Xinhai year of the sexagenary cycle | Statement: [Xīnhài Gémìng, hasCalendarReference, Xinhai year of the sexagenary cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalendarReference Context triple: [Xīnhài Gémìng, hasCalendarReference, Xinhai year of the sexagenary cycle]
-
A.
hasCalendarAssociation
chosen
Indicates that there is a defined relationship or linkage between an entity and a calendar or calendar-related item (such as an event, schedule, or time period).
-
B.
hasCalendarStructure
Indicates that something possesses or follows a specific calendar-based organizational structure (e.g., dates, months, or scheduling framework).
-
C.
hasCalendarFunction
Indicates that an entity possesses or supports a calendar-related capability or functionality.
-
D.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
E.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: May 3, 2026, 4:21 p.m.