Triple
T6854790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess |
E158109
|
entity |
| Predicate | titleStyleInUK |
P17682
|
FINISHED |
| Object | The Most Honourable |
—
|
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 Most Honourable | Statement: [Marquess, titleStyleInUK, The Most Honourable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleStyleInUK Context triple: [Marquess, titleStyleInUK, The Most Honourable]
-
A.
titleHolderStyle
chosen
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to another entity.
-
B.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
C.
includesTitleStyle
Indicates that one entity incorporates or specifies a particular style or formatting for a title associated with it.
-
D.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
E.
titlePattern
Indicates that there is a specific structural or textual pattern that the title of an entity is expected to follow.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d86d5a54819088537ada9f8d1105 |
completed | March 27, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.