Triple
T37378779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cretin-Derham Hall Raiders softball team |
E928368
|
entity |
| Predicate | playsHomeGamesFor |
P189758
|
FINISHED |
| Object | Cretin-Derham Hall |
—
|
NE NERFINISHED |
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: Cretin-Derham Hall | Statement: [Cretin-Derham Hall Raiders softball team, playsHomeGamesFor, Cretin-Derham Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsHomeGamesFor Context triple: [Cretin-Derham Hall Raiders softball team, playsHomeGamesFor, Cretin-Derham Hall]
-
A.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
B.
playsSelectHomeGamesAt
Indicates that an entity (typically a sports team) holds some or all of its designated home games at a specified venue or location.
-
C.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
-
D.
playsHomeConferenceGamesIn
Indicates that a team plays its home conference games at a specified location or venue.
-
E.
playsForHouseTeam
Indicates that an individual is a member of and participates as a player on a particular house team.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 3, 2026, 4:16 p.m.