Triple
T26595627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UConn Huskies women's volleyball |
E667481
|
entity |
| Predicate | jerseySupplier |
P161941
|
FINISHED |
| Object | Nike |
—
|
NE NERFINISHED |
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: Nike | Statement: [UConn Huskies women's volleyball, jerseySupplier, Nike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseySupplier Context triple: [UConn Huskies women's volleyball, jerseySupplier, Nike]
-
A.
jerseyUsage
Indicates that an entity uses, wears, or is associated with a particular jersey in a given context.
-
B.
jerseyFeature
Indicates that one entity has a specific design element, attribute, or characteristic present on a jersey.
-
C.
jersey
Indicates that one entity is the jersey (sports uniform top) associated with, worn by, or representing another entity.
-
D.
jerseyDescription
Indicates that a textual description is provided for a particular jersey, such as its appearance, style, or distinguishing features.
-
E.
jerseyStatus
Indicates the current condition, availability, or usage state of a jersey in relation to an 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 2:10 a.m.