Triple
T33018940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LBSU women's volleyball |
E844850
|
entity |
| Predicate | playsHomeMatches |
P91575
|
FINISHED |
| Object | on campus |
—
|
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: on campus | Statement: [LBSU women's volleyball, playsHomeMatches, on campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsHomeMatches Context triple: [LBSU women's volleyball, playsHomeMatches, on campus]
-
A.
playedHomeMatchesIn
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
-
B.
playsDomesticLeague
Indicates that an athlete or team participates in competitive matches within a specified country's primary league system.
-
C.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
-
D.
playsTestMatchesAgainst
Indicates that one entity participates in test cricket matches as an opponent against another entity.
-
E.
playsSelectHomeGamesAt
chosen
Indicates that an entity (typically a sports team) holds some or all of its designated home games at a specified venue or location.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:23 a.m.