Triple
T29394752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint John's Johnnies football |
E745463
|
entity |
| Predicate | rivalryState |
P107240
|
FINISHED |
| Object | Minnesota |
—
|
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: Minnesota | Statement: [Saint John's Johnnies football, rivalryState, Minnesota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryState Context triple: [Saint John's Johnnies football, rivalryState, Minnesota]
-
A.
rivalryStatus
Indicates a competitive or adversarial relationship between entities, often involving ongoing opposition or contention.
-
B.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
-
C.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
D.
isIntraStateRivalryOf
chosen
Indicates that there is a rivalry occurring within the same state or internal political unit between the related entities.
-
E.
rivalryCharacterizedBy
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
- 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_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:45 p.m.