Triple
T35913290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | summer solstice |
E1038678
|
entity |
| Predicate | relatedCalendarSystem |
P97978
|
FINISHED |
| Object | Gregorian calendar |
E4645
|
NE 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: Gregorian calendar | Statement: [summer solstice, relatedCalendarSystem, Gregorian calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCalendarSystem Context triple: [summer solstice, relatedCalendarSystem, Gregorian calendar]
-
A.
usedInCalendarSystem
chosen
Indicates that something (such as a time unit, era, or convention) is employed as part of a particular calendar system.
-
B.
hasNumberOfWeekSystems
Indicates the relationship that specifies how many distinct week-based systems are associated with or used by a given entity.
-
C.
usedCalendarReform
Indicates that one entity adopted or implemented a particular calendar reform associated with another entity.
-
D.
holidayDateSystem
Indicates the system or convention used to determine and represent the date on which a holiday occurs.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- F. None of above.
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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae2faecc819081260405036da5df |
completed | June 22, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.