Triple
T31974201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borsalino |
E816402
|
entity |
| Predicate | posterCharacterizes |
P173069
|
FINISHED |
| Object | iconic fedora imagery |
—
|
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: iconic fedora imagery | Statement: [Borsalino, posterCharacterizes, iconic fedora imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posterCharacterizes Context triple: [Borsalino, posterCharacterizes, iconic fedora imagery]
-
A.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
B.
plotCharacter
Indicates a relationship where a character plays a role or participates in the narrative plot of a story or work.
-
C.
characterPersona
Indicates that one entity embodies, represents, or assumes the persona, role, or character identity specified by another entity.
-
D.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
E.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b343b8948190993241cef00000dd |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:10 a.m.