Triple
T19171919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffragan Bishop of West Texas |
E469341
|
entity |
| Predicate | mayStyleAs |
P69527
|
FINISHED |
| Object | The Right Reverend |
—
|
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: The Right Reverend | Statement: [Suffragan Bishop of West Texas, mayStyleAs, The Right Reverend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayStyleAs Context triple: [Suffragan Bishop of West Texas, mayStyleAs, The Right Reverend]
-
A.
mayHoldStyle
chosen
Indicates that an entity is permitted or able to possess or be associated with a particular style or stylistic attribute.
-
B.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
C.
usesAsStyleOf
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
-
D.
styledAs
Indicates that one entity is presented, formatted, or designed in the manner, appearance, or aesthetic of another entity.
-
E.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16481948190973067eb854da237 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.