Triple
T8306385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husky Stadium |
E194472
|
entity |
| Predicate | hasNamingOrigin |
P3325
|
FINISHED |
| Object | named for Washington Huskies athletics program |
—
|
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: named for Washington Huskies athletics program | Statement: [Husky Stadium, hasNamingOrigin, named for Washington Huskies athletics program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamingOrigin Context triple: [Husky Stadium, hasNamingOrigin, named for Washington Huskies athletics program]
-
A.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
D.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
E.
hasGivenNameBasis
Indicates that one entity’s given name is derived from, based on, or formed using another entity (such as a name, word, or person) as its basis.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.