Triple
T14115850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight Commander (AK) |
E339772
|
entity |
| Predicate | styleEntitlement |
P1607
|
FINISHED |
| Object | Sir |
—
|
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: Sir | Statement: [Knight Commander (AK), styleEntitlement, Sir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleEntitlement Context triple: [Knight Commander (AK), styleEntitlement, Sir]
-
A.
styleGranted
chosen
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
-
B.
styleDetail
Indicates a relationship where specific stylistic characteristics or attributes of something are described or specified in detail.
-
C.
styleRestriction
Indicates a constraint or limitation imposed on the manner, form, or stylistic way in which something may be expressed, presented, or performed.
-
D.
styleHeldBy
Indicates that a particular style, design, or aesthetic is possessed, used, or embodied by a specific entity.
-
E.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6010a03c81909f5f160f8d1fa8fa |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.