Triple
T9880441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherry Crusade |
E180788
|
entity |
| Predicate | homeVenueSupported |
P87779
|
FINISHED |
| Object | Temple Owls men's basketball home games |
—
|
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: Temple Owls men's basketball home games | Statement: [Cherry Crusade, homeVenueSupported, Temple Owls men's basketball home games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueSupported Context triple: [Cherry Crusade, homeVenueSupported, Temple Owls men's basketball home games]
-
A.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
B.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
C.
homeArenaSupported
Indicates that an entity is supported or hosted in its designated home arena or primary venue.
-
D.
homeVenueCountry
Indicates the country in which an entity’s primary or home venue is located.
-
E.
homeMeetsVenue
chosen
Indicates that a home team plays its scheduled match at a specified venue.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4146fe881908f9fc553dfca31e1 |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:38 p.m.