Triple
T22852943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boknal |
E566399
|
entity |
| Predicate | relatedToSolarTerm |
P91627
|
FINISHED |
| Object | Gyeongchip |
—
|
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: Gyeongchip | Statement: [Boknal, relatedToSolarTerm, Gyeongchip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToSolarTerm Context triple: [Boknal, relatedToSolarTerm, Gyeongchip]
-
A.
solarTermRelation
chosen
Indicates a temporal relationship between entities based on their association with specific solar terms or positions within the solar term cycle.
-
B.
solarTermInterval
Indicates the time span or interval associated with a specific solar term within a calendar or astronomical cycle.
-
C.
relatedHoliday
Indicates that there is an association or connection between two holidays, such as thematic, temporal, cultural, or contextual relatedness.
-
D.
solarTermCount
Indicates the number of solar terms associated with or assigned to a given entity or context.
-
E.
timeRelationToSpringTerm
Indicates how a given time or event is positioned relative to the spring academic term (e.g., before, during, or after it).
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eba65a881908c484262c3ee5212 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.