Triple
T1678195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Bean |
E36279
|
entity |
| Predicate | signatureOutfit |
P15592
|
FINISHED |
| Object | brown tweed jacket |
—
|
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: brown tweed jacket | Statement: [Mr. Bean, signatureOutfit, brown tweed jacket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureOutfit Context triple: [Mr. Bean, signatureOutfit, brown tweed jacket]
-
A.
signatureStyle
Indicates the characteristic way in which an entity typically signs its name or marks documents, distinguishing its unique signing pattern or format.
-
B.
typicallyWornWith
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
-
C.
garmentType
Indicates the specific kind or category of garment associated with an entity.
-
D.
signatureTheme
chosen
Indicates that something serves as a distinctive, defining theme strongly associated with a particular entity or context.
-
E.
alsoWornIn
Indicates that an item of clothing or accessory is additionally worn in another context, location, or time beyond the primary one mentioned.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.