Triple
T2246251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary "Eggsy" Unwin |
E49510
|
entity |
| Predicate | notableOutfit |
P36462
|
FINISHED |
| Object | bespoke suit |
—
|
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: bespoke suit | Statement: [Gary "Eggsy" Unwin, notableOutfit, bespoke suit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOutfit Context triple: [Gary "Eggsy" Unwin, notableOutfit, bespoke suit]
-
A.
notableTie
Indicates a significant connection or association between entities that is noteworthy or distinguished in some context.
-
B.
alsoWornIn
Indicates that an item of clothing or accessory is additionally worn in another context, location, or time beyond the primary one mentioned.
-
C.
typicallyWornWith
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
-
D.
wardrobeFeature
Indicates that a wardrobe possesses or includes a specific feature, attribute, or functional element.
-
E.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ea75d881909d4e176a432f32e8 |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.