Triple
T748531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division II Wrestling |
E15394
|
entity |
| Predicate | usesChampionshipVenueType |
P10640
|
FINISHED |
| Object | neutral site arena |
—
|
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: neutral site arena | Statement: [NCAA Division II Wrestling, usesChampionshipVenueType, neutral site arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChampionshipVenueType Context triple: [NCAA Division II Wrestling, usesChampionshipVenueType, neutral site arena]
-
A.
containsStadium
Indicates that a location or area includes a stadium within its boundaries or premises.
-
B.
hasSportsTeamVenueFor
Indicates that a venue serves as the home or hosting location for a particular sports team.
-
C.
hasMajorVenue
Indicates that an entity is associated with a primary or principal venue where its main activities or events take place.
-
D.
supportsChampionshipsOf
Indicates that one entity provides backing, resources, or endorsement for the championships associated with another entity.
-
E.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62f31888190b80cb0a7220f8d80 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.