Triple
T12767416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee National Holiday |
E305159
|
entity |
| Predicate | attendees |
P2636
|
FINISHED |
| Object | Cherokee Nation citizens |
—
|
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: Cherokee Nation citizens | Statement: [Cherokee National Holiday, attendees, Cherokee Nation citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendees Context triple: [Cherokee National Holiday, attendees, Cherokee Nation citizens]
-
A.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
B.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
C.
attendance
chosen
Indicates the relationship between an event and the people who are present at or participate in that event.
-
D.
customaryAttendee
Indicates that an entity habitually or traditionally attends a particular event, gathering, or type of occasion.
-
E.
organizers
Indicates that one or more entities are responsible for planning, coordinating, or managing an event, activity, or group.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df3b2f88190b37b696400178795 |
completed | April 10, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.