Triple
T33237900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNZM |
E850881
|
entity |
| Predicate | entitlesHolderToStyle |
P176235
|
FINISHED |
| Object | Sir |
—
|
NE NERFINISHED |
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: Sir | Statement: [KNZM, entitlesHolderToStyle, Sir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entitlesHolderToStyle Context triple: [KNZM, entitlesHolderToStyle, Sir]
-
A.
entitlesStyle
Indicates that one entity grants or specifies a particular style or manner of presentation for another entity.
-
B.
titleHolderStyle
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to another entity.
-
C.
styleHeldBy
Indicates that a particular style, design, or aesthetic is possessed, used, or embodied by a specific entity.
-
D.
associatedTitleStyle
Indicates a relationship where one entity is linked to a particular title style that defines how its title should be presented or formatted.
-
E.
titleStyleAdopted
Indicates that a particular style or format for a title has been chosen and put into use for an 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:31 a.m.