Triple
T28870705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fisher Stadium |
E732132
|
entity |
| Predicate | hostsRivalry |
P126608
|
FINISHED |
| Object | Lafayette–Lehigh football rivalry |
—
|
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: Lafayette–Lehigh football rivalry | Statement: [Fisher Stadium, hostsRivalry, Lafayette–Lehigh football rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsRivalry Context triple: [Fisher Stadium, hostsRivalry, Lafayette–Lehigh football rivalry]
-
A.
conferenceRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
-
B.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
C.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
D.
hasLocalRivalryVenueWith
chosen
Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
-
E.
nicknameOfRivalryBetween
Indicates that one entity is a nickname or informal title used to refer to a particular rivalry between other 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:32 a.m.