Triple
T6965909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirWair |
E161486
|
entity |
| Predicate | isBrandedOn |
P11989
|
FINISHED |
| Object | Dr. Martens shoe soles |
—
|
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: Dr. Martens shoe soles | Statement: [AirWair, isBrandedOn, Dr. Martens shoe soles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBrandedOn Context triple: [AirWair, isBrandedOn, Dr. Martens shoe soles]
-
A.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
B.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
C.
usesBrandCharacter
Indicates that one entity employs or features another entity’s brand character (such as a mascot or branded persona) in its materials, products, or communications.
-
D.
hasBranding
chosen
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
E.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db121174819098e73e45f6c9cc91 |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.