Triple
T25765046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Browns shoes |
E648857
|
entity |
| Predicate | oftenWornWith |
P27860
|
FINISHED |
| Object | Cleveland Browns jerseys |
—
|
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: Cleveland Browns jerseys | Statement: [Cleveland Browns shoes, oftenWornWith, Cleveland Browns jerseys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenWornWith Context triple: [Cleveland Browns shoes, oftenWornWith, Cleveland Browns jerseys]
-
A.
typicallyWornWith
chosen
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
-
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.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
-
D.
notWornWith
Indicates that one item is not worn at the same time as another item, implying mutual exclusivity in being worn together.
-
E.
typicallyWornBy
Indicates that something (such as an item or garment) is most commonly or characteristically worn by a particular type of person or group.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 22, 2026, 5:09 a.m.