Triple
T15174124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N95 |
E362560
|
entity |
| Predicate | supportsN-GageGames |
P103411
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nokia N95, supportsN-GageGames, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsN-GageGames Context triple: [Nokia N95, supportsN-GageGames, true]
-
A.
supportsGames
chosen
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
B.
seriesOfSupportedGame
Indicates that one entity is a series or collection consisting of multiple games that are supported by another entity (such as a platform, service, or system).
-
C.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
-
D.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
E.
supportsGameCubeControllers
Indicates that an entity is compatible with and can be used with GameCube controllers.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006501b488190a2ab09dbf1532571 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.