Triple
T25629263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Eight Deer Jaguar Claw |
E642527
|
entity |
| Predicate | calendarName |
P158940
|
FINISHED |
| Object | Eight Deer |
—
|
NE NERFINISHED |
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: Eight Deer | Statement: [Lord Eight Deer Jaguar Claw, calendarName, Eight Deer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarName Context triple: [Lord Eight Deer Jaguar Claw, calendarName, Eight Deer]
-
A.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
B.
nameDayCalendar
Indicates a calendar system that specifies which personal names are celebrated on particular days (name days).
-
C.
calendarFeature
Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
-
D.
calendarCategory
Indicates the classification or grouping assigned to calendar entries based on their type, purpose, or context.
-
E.
calendarUsedFor
Indicates that a particular calendar is employed or applied for a specific purpose, context, or activity.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa260734819080d7d32c6912d267 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 5:16 p.m.