Triple
T8563994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Louis of Luxembourg |
E202757
|
entity |
| Predicate | weddingReligiousDate |
P198
|
FINISHED |
| Object | 2006-09-29 |
—
|
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: 2006-09-29 | Statement: [Prince Louis of Luxembourg, weddingReligiousDate, 2006-09-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weddingReligiousDate Context triple: [Prince Louis of Luxembourg, weddingReligiousDate, 2006-09-29]
-
A.
religiousCouncilDate
Indicates the date on which a religious council or formal ecclesiastical assembly took place.
-
B.
ritualDate
Indicates the specific date on which a ritual or ceremonial event takes place.
-
C.
marriageDate
chosen
Indicates the specific date on which two entities entered into a marital relationship.
-
D.
religiousCalendar
Indicates that there is an association between an entity and a system of dates and observances defined by a particular religion or religious tradition.
-
E.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d11274819099cc33a21a993a1f |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.