Triple
T6262501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Harewood |
E140333
|
entity |
| Predicate | styleHeldBy |
P69789
|
FINISHED |
| Object | wife of the Earl of Harewood |
—
|
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: wife of the Earl of Harewood | Statement: [Countess of Harewood, styleHeldBy, wife of the Earl of Harewood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleHeldBy Context triple: [Countess of Harewood, styleHeldBy, wife of the Earl of Harewood]
-
A.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
B.
styleInFull
Indicates that something is presented, written, or expressed in its complete, unabbreviated, or fully detailed form.
-
C.
styleGranted
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
-
D.
styleCategory
Indicates the stylistic classification or genre category that an item, work, or entity belongs to.
-
E.
styledAs
Indicates that one entity is presented, formatted, or designed in the manner, appearance, or aesthetic of another entity.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06386a7b48190b032edd12078c5bc |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:25 p.m.