Triple
T15999559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GD-ROM |
E388059
|
entity |
| Predicate | mainCompetitorMediumAtLaunch |
P1375
|
FINISHED |
| Object | DVD-ROM |
—
|
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: DVD-ROM | Statement: [GD-ROM, mainCompetitorMediumAtLaunch, DVD-ROM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCompetitorMediumAtLaunch Context triple: [GD-ROM, mainCompetitorMediumAtLaunch, DVD-ROM]
-
A.
competingPlatform
Indicates that two platforms operate in the same market or domain and vie against each other to attract the same users, customers, or resources.
-
B.
successorInMarket
Indicates that one entity has taken over or followed another in serving the same market or customer base.
-
C.
competesWith
chosen
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
D.
secondaryCompetition
Indicates that one entity participates in or is involved with a secondary or subordinate competition relative to a primary one.
-
E.
attractsCompetitorsFrom
Indicates that one entity draws or lures competitors away from another entity or location.
- 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.