Triple
T6823674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kofi |
E156959
|
entity |
| Predicate | hasNameDayAssociation |
P59993
|
FINISHED |
| Object | Friday birth in Akan culture |
—
|
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: Friday birth in Akan culture | Statement: [Kofi, hasNameDayAssociation, Friday birth in Akan culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayAssociation Context triple: [Kofi, hasNameDayAssociation, Friday birth in Akan culture]
-
A.
hasNameDayRelation
chosen
Indicates a relationship where a person’s name is associated with a specific name day or feast day in a calendar.
-
B.
hasNameDay
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
C.
hasNameDayContext
Indicates that an entity’s name day is interpreted or celebrated within a specific contextual framework (such as culture, calendar system, or tradition).
-
D.
nameDayExists
Indicates that there exists a recognized name day associated with a given name (and possibly date or locale).
-
E.
hasHolidayAssociation
Indicates a relationship where something is connected or related to a holiday, such as by theme, usage, or occurrence.
- 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d580ca448190aa6d52908ca50e39 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.