Triple
T19208881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clemson Tigers baseball |
E480305
|
entity |
| Predicate | isHistoricallySuccessfulInACC |
P83536
|
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, isHistoricallySuccessfulInACC, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricallySuccessfulInACC Context triple: [Clemson Tigers baseball, isHistoricallySuccessfulInACC, yes]
-
A.
isHistoricallySuccessful
Indicates that an entity has achieved notable success or positive outcomes over a significant period in the past.
-
B.
hasPostseasonHistory
Indicates that an entity has a record of participation or performance in postseason or playoff competitions.
-
C.
hasNotableSuccessIn
chosen
Indicates that an entity has achieved significant or widely recognized success in a particular field, activity, or domain.
-
D.
hasHistoricalReliability
Indicates that something is supported by credible historical evidence and is considered trustworthy as an account of past events.
-
E.
hasNeverBeenRelegatedFrom
Indicates that the subject has not at any time been demoted or relegated from the specified league, division, or level of competition.
- 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.