Triple
T30328412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Genesis software library |
E771404
|
entity |
| Predicate | includesSoftwareType |
P83486
|
FINISHED |
| Object | video 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: video games | Statement: [Sega Genesis software library, includesSoftwareType, video games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSoftwareType Context triple: [Sega Genesis software library, includesSoftwareType, video games]
-
A.
hasSoftwareType
chosen
Indicates that an entity is associated with or classified under a particular type or category of software.
-
B.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
C.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
-
D.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
-
E.
targetedSoftware
Indicates that a particular piece of software is the specific focus or target of an action, operation, or effect.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
Created at: April 29, 2026, 7:53 p.m.