Triple
T20165681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Color TV-Game series |
E491819
|
entity |
| Predicate | gameStorage |
P138923
|
FINISHED |
| Object | built-in games |
—
|
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: built-in games | Statement: [Color TV-Game series, gameStorage, built-in games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameStorage Context triple: [Color TV-Game series, gameStorage, built-in games]
-
A.
game4Save
Indicates a relationship where a game is being saved or a save action/state is associated with a particular game instance.
-
B.
homeGamesState
Indicates the state or location context in which a team's home games are played.
-
C.
Game7Save
Indicates a game situation where a player or team successfully preserves a lead in a decisive seventh game, securing the win under high-pressure, series-deciding conditions.
-
D.
gamingSpace
Indicates a relationship where a space, area, or environment is designated or used specifically for gaming activities.
-
E.
gamePlayed
Indicates that a particular game is or was played by an entity (such as a person, team, or group) during a specific event or time.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:35 p.m.