Triple
T30057981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baronet of Ballentaylor and Ballylemon |
E763786
|
entity |
| Predicate | titleStyleForWife |
P172323
|
FINISHED |
| Object | Lady |
—
|
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: Lady | Statement: [Baronet of Ballentaylor and Ballylemon, titleStyleForWife, Lady]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleStyleForWife Context triple: [Baronet of Ballentaylor and Ballylemon, titleStyleForWife, Lady]
-
A.
titleStyleOfWifeOfHolder
chosen
Indicates the style or form of the title that is specifically used for the wife of the title holder.
-
B.
titleStyleAdopted
Indicates that a particular style or format for a title has been chosen and put into use for an entity.
-
C.
spouseStyle
Indicates a stylistic or fashion-related relationship or influence that exists between spouses.
-
D.
titleHolderStyle
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to another entity.
-
E.
titleStyleInFull
Indicates that the specified title is presented in its complete, unabridged form, including all stylistic elements or formatting.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 29, 2026, 6:57 p.m.