Triple
T6412168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cincinnati Reds–Pittsburgh Pirates rivalry |
E127731
|
entity |
| Predicate | eraOfIntenseCompetition |
P22371
|
FINISHED |
| Object | 1970–1979 |
—
|
LITERAL 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: 1970–1979 | Statement: [Cincinnati Reds–Pittsburgh Pirates rivalry, eraOfIntenseCompetition, 1970–1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfIntenseCompetition Context triple: [Cincinnati Reds–Pittsburgh Pirates rivalry, eraOfIntenseCompetition, 1970–1979]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionEra
chosen
Indicates the historical or contextual period during which a particular competition or competitive event took place.
-
C.
levelOfCompetition
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
-
D.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
E.
primaryCompetition
Indicates that one entity is the main or most significant competitor of another within a given market, domain, or context.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068d228208190ba05eeb7707482fe |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.