Triple
T9279925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phyllis Smith |
E223040
|
entity |
| Predicate | cheeredFor |
P3720
|
FINISHED |
| Object | St. Louis Cardinals (football) cheerleaders |
—
|
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: St. Louis Cardinals (football) cheerleaders | Statement: [Phyllis Smith, cheeredFor, St. Louis Cardinals (football) cheerleaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cheeredFor Context triple: [Phyllis Smith, cheeredFor, St. Louis Cardinals (football) cheerleaders]
-
A.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
B.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
C.
wonFor
Indicates that one entity received an award, prize, or recognition specifically on behalf of or representing another entity.
-
D.
supporter
chosen
Indicates a relationship where one entity backs, advocates for, or provides assistance to another entity, often in an ongoing or affiliative way.
-
E.
isCelebratoryOf
Indicates that something expresses celebration, honor, or festive recognition directed toward a particular event, person, or occasion.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07cc79508190954defbef0d82a64 |
completed | April 1, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.