Triple
T26298597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pretty Boy |
E661485
|
entity |
| Predicate | bearerNotableStyle |
P140235
|
FINISHED |
| Object | defensive boxer |
—
|
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: defensive boxer | Statement: [Pretty Boy, bearerNotableStyle, defensive boxer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerNotableStyle Context triple: [Pretty Boy, bearerNotableStyle, defensive boxer]
-
A.
notableStyleFeature
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
-
B.
notableSubstyle
Indicates that one style is a notable or distinct subcategory within another broader style.
-
C.
hasNotableBearerStyle
Indicates that a particular style, form, or variant is notably associated with a specific bearer (such as a person, group, or entity) as a distinguishing characteristic.
-
D.
notableHolderFullStyle
Indicates that a person is a notable holder of a title, position, or honor, expressed using their full formal style.
-
E.
bearerStyleCharacteristic
chosen
Indicates that a bearer (such as a person or object) exhibits or is associated with a particular style-related characteristic.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 26, 2026, 10:14 p.m.