Triple
T31306433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee traditional religion |
E798344
|
entity |
| Predicate | hasCalendarAssociation |
P197024
|
FINISHED |
| Object | agricultural cycles |
—
|
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: agricultural cycles | Statement: [Cherokee traditional religion, hasCalendarAssociation, agricultural cycles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalendarAssociation Context triple: [Cherokee traditional religion, hasCalendarAssociation, agricultural cycles]
-
A.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
hasHolidayAssociation
Indicates a relationship where something is connected or related to a holiday, such as by theme, usage, or occurrence.
-
C.
belongsToCalendar
Indicates that an event or item is associated with and contained within a specific calendar.
-
D.
hasCalendarStructure
Indicates that something possesses or follows a specific calendar-based organizational structure (e.g., dates, months, or scheduling framework).
-
E.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69fe744e9ee081909b362fc8609bc744 |
completed | May 8, 2026, 11:39 p.m. |
Created at: April 29, 2026, 9:14 p.m.