Triple
T3185087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Steelers vs Baltimore Ravens |
E66678
|
entity |
| Predicate | typicalGameStyle |
P3775
|
FINISHED |
| Object | low-scoring |
—
|
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: low-scoring | Statement: [Pittsburgh Steelers vs Baltimore Ravens, typicalGameStyle, low-scoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGameStyle Context triple: [Pittsburgh Steelers vs Baltimore Ravens, typicalGameStyle, low-scoring]
-
A.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
B.
traditionalGame
Indicates that the relationship involves playing, practicing, or being associated with a game that is rooted in longstanding cultural or historical traditions.
-
C.
typicalGameLocation
Indicates the usual or characteristic place where a game is played or takes place.
-
D.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
E.
competitiveGame
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.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6c1341081909793f8d05fddfd5e |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.