Triple
T29394781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Catherine Wildcats |
E745464
|
entity |
| Predicate | hasRivalInstitution |
P14804
|
FINISHED |
| Object | University of St. Thomas (Tommies) |
—
|
NE NERFINISHED |
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: University of St. Thomas (Tommies) | Statement: [St. Catherine Wildcats, hasRivalInstitution, University of St. Thomas (Tommies)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalInstitution Context triple: [St. Catherine Wildcats, hasRivalInstitution, University of St. Thomas (Tommies)]
-
A.
rivalInstitution
chosen
Indicates that one institution is in a state of competition or opposition with another institution.
-
B.
hasRivalState
Indicates that one state maintains a rivalry or competitive opposition with another state.
-
C.
hasForeignRival
Indicates that an entity has at least one rival that is based in or originates from a different country or foreign jurisdiction.
-
D.
hasRivalStand
Indicates that one entity maintains a competing or opposing stand, position, or operation in relation to another entity.
-
E.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 2:45 p.m.