Triple
T23571041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sandberg Game |
E580111
|
entity |
| Predicate | featuredTeamPlayer |
P42751
|
FINISHED |
| Object | Ryne Sandberg |
—
|
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: Ryne Sandberg | Statement: [The Sandberg Game, featuredTeamPlayer, Ryne Sandberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredTeamPlayer Context triple: [The Sandberg Game, featuredTeamPlayer, Ryne Sandberg]
-
A.
featuresPlayers
Indicates that something includes or showcases one or more players as part of its content or composition.
-
B.
featuresPlayersFrom
Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
-
C.
featuresPlayer
chosen
Indicates that something includes or prominently presents a particular player as part of its content or composition.
-
D.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
E.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
- 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_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. |
Created at: April 17, 2026, 6:36 p.m.