Triple
T18948256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan |
E463572
|
entity |
| Predicate | hasNameDayInNetherlands |
P910
|
FINISHED |
| Object | variesByTradition |
—
|
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: variesByTradition | Statement: [Jan, hasNameDayInNetherlands, variesByTradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayInNetherlands Context triple: [Jan, hasNameDayInNetherlands, variesByTradition]
-
A.
hasNameInDutch
Indicates that an entity is associated with a specific name or label expressed in the Dutch language.
-
B.
hasNameDay
chosen
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
C.
hasNameDayInformation
Indicates that there exists associated information about a person’s name day, such as the date or related observances.
-
D.
hasNameInBelgium
Indicates that an entity is known or referred to by a particular name specifically within the context of Belgium.
-
E.
hasLaterDutchName
Indicates that an entity was known by a different Dutch name at a later time than its original or earlier Dutch name.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d540e57c8190bb17fff6d4254320 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.