Triple
T19208898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clemson Tigers baseball |
E480305
|
entity |
| Predicate | playsNonConferenceSchedule |
P48266
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Clemson Tigers baseball, playsNonConferenceSchedule, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsNonConferenceSchedule Context triple: [Clemson Tigers baseball, playsNonConferenceSchedule, yes]
-
A.
nonConferencePlay
chosen
Indicates games, matches, or competitions played outside of a team’s regular conference or league schedule.
-
B.
playsConferenceTournament
Indicates that an entity participates in a conference-level tournament competition.
-
C.
isNonFootballConference
Indicates that an entity (such as a school or team) belongs to a conference that does not participate in football competition.
-
D.
isConferenceGame
Indicates that a particular game is played between teams within the same athletic conference and counts toward conference standings.
-
E.
playsCollegeBasketballIn
Indicates that an individual is a member of and competes for a college or university’s basketball team located at a specified institution or place.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9a000188190afb762ea24bc3deb |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:20 p.m.