Triple
T26260135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscountess Althorp |
E656823
|
entity |
| Predicate | transferredOnMarriageChange |
P136637
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Viscountess Althorp, transferredOnMarriageChange, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredOnMarriageChange Context triple: [Viscountess Althorp, transferredOnMarriageChange, true]
-
A.
membershipChangeOnMarriage
chosen
Indicates a change in an entity’s membership status in some group or organization that occurs as a direct result of a marriage event.
-
B.
marriageStatusChange
Indicates a change in an entity’s marital status from one state to another at a particular point in time.
-
C.
marriedInto
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
D.
spouseLaterMarriedBy
Indicates that one’s spouse subsequently entered into a later marriage with another partner.
-
E.
spouseMovement
Indicates a movement or relocation event involving a person and their spouse, such as moving together or one moving to join the other.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 26, 2026, 9:10 p.m.