Triple
T23571045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sandberg Game |
E580111
|
entity |
| Predicate | opposingStarPlayer |
P153212
|
FINISHED |
| Object | Bruce Sutter |
—
|
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: Bruce Sutter | Statement: [The Sandberg Game, opposingStarPlayer, Bruce Sutter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingStarPlayer Context triple: [The Sandberg Game, opposingStarPlayer, Bruce Sutter]
-
A.
opponentStarPlayerTeam
Indicates that the referenced team is the one for which the opponent’s star player plays.
-
B.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
C.
opponentInScenario
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
-
D.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
E.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
- F. None of above. chosen
Provenance (4 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd34c088190bf4f736f1066c920 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:36 p.m.