Triple
T36202742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard–Yale softball rivalry |
E1047310
|
entity |
| Predicate | reflectsRivalry |
P29010
|
FINISHED |
| Object | Harvard–Yale 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: Harvard–Yale rivalry | Statement: [Harvard–Yale softball rivalry, reflectsRivalry, Harvard–Yale rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsRivalry Context triple: [Harvard–Yale softball rivalry, reflectsRivalry, Harvard–Yale rivalry]
-
A.
rivalryCharacterizedBy
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
-
B.
portraysRivalry
Indicates that one entity depicts or represents a relationship of competition or antagonism between two or more entities.
-
C.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
D.
typeOfRivalry
chosen
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
-
E.
involvesRivalryBetween
Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.