Triple
T38691124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lodewijck |
E949264
|
entity |
| Predicate | nameDayRelatedForm |
P114002
|
FINISHED |
| Object | Lodewijk |
—
|
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: Lodewijk | Statement: [Lodewijck, nameDayRelatedForm, Lodewijk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameDayRelatedForm Context triple: [Lodewijck, nameDayRelatedForm, Lodewijk]
-
A.
nameDayBaseForm
chosen
Indicates the base or canonical form of a name used specifically for name-day (saint’s day) associations or celebrations.
-
B.
namesDay
Indicates that one entity is the name assigned to a particular day (such as a weekday or holiday) associated with another entity.
-
C.
nameDayAssociatedConcept
Indicates an association between a name day and a related concept, such as a theme, symbol, idea, or contextual meaning linked to that name day.
-
D.
nameDayCalendar
Indicates a calendar system that specifies which personal names are celebrated on particular days (name days).
-
E.
nameDayStatus
Indicates the status or condition of a person's name day (e.g., whether it is set, active, upcoming, or celebrated).
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:33 p.m.