Triple
T2883565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabi |
E59452
|
entity |
| Predicate | hasNameDayRelationTo |
P910
|
FINISHED |
| Object | name day of Gabriel |
—
|
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: name day of Gabriel | Statement: [Gabi, hasNameDayRelationTo, name day of Gabriel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayRelationTo Context triple: [Gabi, hasNameDayRelationTo, name day of Gabriel]
-
A.
hasNameDay
chosen
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
B.
nameDayRegion
Indicates the region or geographic area in which a particular name day is observed or recognized.
-
C.
namesDay
Indicates that one entity is the name assigned to a particular day (such as a weekday or holiday) associated with another entity.
-
D.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
E.
hasHonorificNamesake
Indicates that an entity is named in honor of another entity, serving as a namesake that recognizes or commemorates the other.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02c238881908f7a349563c388bf |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.