Triple
T3174819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess in the Peerage of England |
E66436
|
entity |
| Predicate | styleOfAddressForWife |
P12836
|
FINISHED |
| Object | Marchioness |
—
|
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: Marchioness | Statement: [Marquess in the Peerage of England, styleOfAddressForWife, Marchioness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfAddressForWife Context triple: [Marquess in the Peerage of England, styleOfAddressForWife, Marchioness]
-
A.
isStyleOfAddress
chosen
Indicates that one term or expression functions as a particular way of addressing or referring to another entity.
-
B.
nameStyle
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
-
C.
styleAfterHusbandDeath
Indicates that an entity adopts or changes its style in response to, or following, the death of its husband.
-
D.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
-
E.
spouseOfHonouree
Indicates that one person is the spouse (married partner) of the honouree.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada670c800819098937783e2b05c7a |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.