Triple
T26272467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UConn Huskies women's track and field |
E660461
|
entity |
| Predicate | indoorOutdoorStatus |
P8552
|
FINISHED |
| Object | outdoor track and field |
—
|
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: outdoor track and field | Statement: [UConn Huskies women's track and field, indoorOutdoorStatus, outdoor track and field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorOutdoorStatus Context triple: [UConn Huskies women's track and field, indoorOutdoorStatus, outdoor track and field]
-
A.
indoorOrOutdoor
chosen
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
B.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
C.
isIndoorOutdoorHybrid
Indicates that something functions as both an indoor and outdoor variant or environment, combining characteristics of each.
-
D.
indoorComponent
Indicates that one entity functions as an indoor part, element, or feature of another entity.
-
E.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e31f5f88190a1e6354a19f33a11 |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:51 p.m.