Triple
T2388018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horatio |
E48874
|
entity |
| Predicate | hasNameDayTraditionIn |
P21133
|
FINISHED |
| Object | some Christian cultures |
—
|
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: some Christian cultures | Statement: [Horatio, hasNameDayTraditionIn, some Christian cultures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayTraditionIn Context triple: [Horatio, hasNameDayTraditionIn, some Christian cultures]
-
A.
hasNameDay
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
B.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
C.
modernHolidayName
Indicates that an entity is known by a holiday name used in modern or contemporary times.
-
D.
isCelebratedIn
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
-
E.
mainlyCelebratedBy
chosen
Indicates that an event, tradition, or occasion is primarily observed or celebrated by a particular group or category of people.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7db4ee08190a5c114e42bc46f70 |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.