Triple
T35500659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armstrong and Miller |
E1025991
|
entity |
| Predicate | notableSketchStyle |
P46274
|
FINISHED |
| Object | character-based sketches |
—
|
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: character-based sketches | Statement: [Armstrong and Miller, notableSketchStyle, character-based sketches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSketchStyle Context triple: [Armstrong and Miller, notableSketchStyle, character-based sketches]
-
A.
hasNotableSketch
Indicates that an entity is associated with a sketch that is considered notable or significant in some context.
-
B.
notableStyleFeature
chosen
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
-
C.
sketchType
Indicates the specific kind or category of sketch associated with an entity or action.
-
D.
artisticStyle
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
E.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.