Triple
T28870200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehigh Mountain Hawks football |
E732120
|
entity |
| Predicate | notableRivalrySeriesName |
P156553
|
FINISHED |
| Object | The Rivalry |
E732131
|
NE 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: The Rivalry | Statement: [Lehigh Mountain Hawks football, notableRivalrySeriesName, The Rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRivalrySeriesName Context triple: [Lehigh Mountain Hawks football, notableRivalrySeriesName, The Rivalry]
-
A.
notableRivalry
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
-
B.
notableRivalryType
Indicates a specific kind or category of rivalry that characterizes the notable competitive relationship between entities.
-
C.
nicknameOfRivalryBetween
chosen
Indicates that one entity is a nickname or informal title used to refer to a particular rivalry between other entities.
-
D.
notableRivalryElement
Indicates that one entity is a significant component, example, or instance within a notable rivalry between two or more entities.
-
E.
hasRivalrySeries
Indicates a recurring competitive relationship or series of contests held between two entities.
- F. None of above.
Provenance (4 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_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24bbc815b481908c4b517a4b53eae2 |
completed | June 7, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
Created at: April 28, 2026, 7:31 a.m.