Triple
T13715218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buren |
E328878
|
entity |
| Predicate | marriageOfWilliamOfOrangeOccurredIn |
P111292
|
FINISHED |
| Object | 1551 |
—
|
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: 1551 | Statement: [Buren, marriageOfWilliamOfOrangeOccurredIn, 1551]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageOfWilliamOfOrangeOccurredIn Context triple: [Buren, marriageOfWilliamOfOrangeOccurredIn, 1551]
-
A.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
-
B.
marriageToHenryIIDate
Indicates the date on which an entity entered into marriage with Henry II.
-
C.
placeOfMarriageToEmpressMatilda
Indicates the location where an individual married Empress Matilda.
-
D.
holderMarriageDateToVictoria
Indicates the date on which the holder entered into marriage with Victoria.
-
E.
marriedToFutureMonarch
Indicates that one person is married to another person who will become a monarch in the future.
- F. None of above. chosen
Provenance (4 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43973cf08190a417d0cca9dd314a |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.