Triple
T15999537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GD-ROM |
E388059
|
entity |
| Predicate | copyProtectionRole |
P82749
|
FINISHED |
| Object | discouraging piracy on Dreamcast |
—
|
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: discouraging piracy on Dreamcast | Statement: [GD-ROM, copyProtectionRole, discouraging piracy on Dreamcast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: copyProtectionRole Context triple: [GD-ROM, copyProtectionRole, discouraging piracy on Dreamcast]
-
A.
protectionRole
chosen
Indicates that one entity serves a protective function or responsibility toward another entity or resource.
-
B.
protectionPolicy
Indicates that one entity establishes or enforces rules or measures to safeguard another entity from harm, loss, or risk.
-
C.
coreProtection
Indicates that an entity provides essential safeguarding or defense for another entity’s central or most critical component.
-
D.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.