Triple
T4795857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard Track and Tennis Center |
E106709
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | track and field venue |
C242
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: track and field venue Context triple: [Harvard Track and Tennis Center, instanceOf, track and field venue]
-
A.
college track and field competition
A college track and field competition is an organized athletic meet where collegiate athletes represent their institutions in a variety of running, jumping, and throwing events under standardized rules and scoring.
-
B.
Olympic competition venue area
An Olympic competition venue area is a designated, secure space that includes the field of play and its immediate surroundings where official Olympic events are conducted according to sport-specific standards.
-
C.
college track and field championship
A college track and field championship is a competitive athletic event where collegiate teams and athletes contest a series of track races and field events to determine individual and team titles at a conference, regional, or national level.
-
D.
sports and recreation facility
chosen
A sports and recreation facility is a place designed and equipped for individuals or groups to engage in physical activities, sports, exercise, and leisure pursuits.
-
E.
track and field relay meet
A track and field relay meet is a competitive event where teams of runners race in sequential legs, passing a baton within designated exchange zones to achieve the fastest overall time.
- F. None of above.
Provenance (1 batch)
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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:22 p.m.