Triple
T2426619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Duff, 6th Earl Fife |
E53542
|
entity |
| Predicate | reasonForDukedom |
P39129
|
FINISHED |
| Object | marriage to Princess Louise of Wales |
—
|
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: marriage to Princess Louise of Wales | Statement: [Alexander Duff, 6th Earl Fife, reasonForDukedom, marriage to Princess Louise of Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDukedom Context triple: [Alexander Duff, 6th Earl Fife, reasonForDukedom, marriage to Princess Louise of Wales]
-
A.
hasNotableDukedom
Indicates that an entity holds or is associated with a dukedom that is considered historically or culturally significant.
-
B.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
C.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
D.
reasonForKnighthood
Indicates the specific cause, achievement, or merit for which an individual was granted knighthood.
-
E.
reasonForAbdication
Indicates the specific cause, motive, or circumstances that led an individual to formally abdicate a position of authority or power.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcc73d2e48190b6ad5f3ee75b74eb |
completed | March 7, 2026, 6:57 a.m. |
Created at: March 6, 2026, 9:42 p.m.