Triple
T33115279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MU Arena |
E847442
|
entity |
| Predicate | hasStudentAthleteFacilities |
P199319
|
FINISHED |
| Object | training rooms |
—
|
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: training rooms | Statement: [MU Arena, hasStudentAthleteFacilities, training rooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentAthleteFacilities Context triple: [MU Arena, hasStudentAthleteFacilities, training rooms]
-
A.
hasNumberOfStudentAthletes
Indicates the relationship that specifies how many student athletes are associated with a given entity.
-
B.
hasAthleticOffices
Indicates that an entity contains or is the location of offices used for managing athletic or sports-related activities.
-
C.
hasSportsInstitute
Indicates that an entity possesses, hosts, or is associated with a sports institute or sports training facility.
-
D.
hasScholarshipAthletes
Indicates that an institution or team includes athletes who are receiving scholarships.
-
E.
studentAthletes
Indicates a relationship where the entities are athletes who are also enrolled as students, combining academic and athletic roles.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69ff2eb0c0888190b0e05a03bf06d388 |
completed | May 9, 2026, 12:55 p.m. |
Created at: May 1, 2026, 1:27 a.m.