Triple
T14242326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscountess Beaconsfield |
E353040
|
entity |
| Predicate | titleHolderSpouseInstanceOf |
P113364
|
FINISHED |
| Object | British statesman |
—
|
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: British statesman | Statement: [Viscountess Beaconsfield, titleHolderSpouseInstanceOf, British statesman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderSpouseInstanceOf Context triple: [Viscountess Beaconsfield, titleHolderSpouseInstanceOf, British statesman]
-
A.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
B.
currentTitleHolderSpouseOf
Indicates that one entity is the current spouse of the individual who presently holds a specified title.
-
C.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
D.
firstHolderSpouseOf
Indicates that the first holder in the relation is the spouse (married partner) of the other holder.
-
E.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6244ad188190b9d9db7914240410 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239bd0f48190ada38c0261e0ef3c |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:08 a.m.