Triple
T4335904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco 49ers–Los Angeles Rams rivalry |
E97461
|
entity |
| Predicate | isIntraConferenceRivalry |
P52336
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [San Francisco 49ers–Los Angeles Rams rivalry, isIntraConferenceRivalry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntraConferenceRivalry Context triple: [San Francisco 49ers–Los Angeles Rams rivalry, isIntraConferenceRivalry, true]
-
A.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
B.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
C.
hasInterconferenceGame
Indicates that there exists a game played between teams belonging to different conferences.
-
D.
conferenceRivalry
chosen
Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
-
E.
isTeamCompetition
Indicates that the competition involves participants organized into teams competing against each other rather than as individuals.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35152bfc88190ab5d53ca38f98d8a |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.