Triple
T4243780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco 49ers–Seattle Seahawks rivalry |
E95476
|
entity |
| Predicate | playEachOther |
P15224
|
FINISHED |
| Object | twice per regular season |
—
|
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: twice per regular season | Statement: [San Francisco 49ers–Seattle Seahawks rivalry, playEachOther, twice per regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playEachOther Context triple: [San Francisco 49ers–Seattle Seahawks rivalry, playEachOther, twice per regular season]
-
A.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
-
B.
competitiveGame
chosen
Indicates a relationship where entities participate in a game or contest in which they compete against each other to win or achieve a higher ranking.
-
C.
plays
Indicates that an entity engages in or performs an activity, game, role, or piece of music.
-
D.
playsFriendlyMatches
Indicates that one entity engages in non-competitive or exhibition-style matches with another entity.
-
E.
playsWith
Indicates that one entity engages in play or recreational activity together with another entity.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e8a676c8190ac2cb59e62613dd9 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.