Triple
T4922276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haloa |
E110492
|
entity |
| Predicate | timeInSolarCalendar |
P60062
|
FINISHED |
| Object | December |
—
|
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: December | Statement: [Haloa, timeInSolarCalendar, December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInSolarCalendar Context triple: [Haloa, timeInSolarCalendar, December]
-
A.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
B.
startDateSidereal
Indicates the sidereal (star-based) date on which an event, period, or state begins.
-
C.
solarTermInterval
Indicates the time span or interval associated with a specific solar term within a calendar or astronomical cycle.
-
D.
solarAlignmentDates
Indicates the specific dates on which an object, structure, or location is aligned in a significant way with the position of the Sun (e.g., sunrise, sunset, solstices, or equinoxes).
-
E.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
- F. None of above. chosen
Provenance (4 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6e482984819087124216738f1e29 |
completed | March 20, 2026, 3:56 p.m. |
Created at: March 20, 2026, 1:30 p.m.