Triple
T2827017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Alexandra, The Honourable Lady Ogilvy |
E54946
|
entity |
| Predicate | spouseStartDate |
P198
|
FINISHED |
| Object | 1963-04-24 |
—
|
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: 1963-04-24 | Statement: [Princess Alexandra, The Honourable Lady Ogilvy, spouseStartDate, 1963-04-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseStartDate Context triple: [Princess Alexandra, The Honourable Lady Ogilvy, spouseStartDate, 1963-04-24]
-
A.
spouseStartTime
Indicates the point in time when two individuals began their spousal (marriage) relationship.
-
B.
spousePositionHeldStartTime
Indicates the date and time when a spouse first began holding a particular position or office.
-
C.
spouseEndTime
Indicates the time or date at which a spousal relationship between two entities ends.
-
D.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
E.
marriageDate
chosen
Indicates the specific date on which two entities entered into a marital relationship.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde94ba848190b2c990936e07e6bb |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.