Triple
T11290533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atari Jaguar |
E267310
|
entity |
| Predicate | developerSupport |
P98330
|
FINISHED |
| Object | limited third-party support |
—
|
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: limited third-party support | Statement: [Atari Jaguar, developerSupport, limited third-party support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerSupport Context triple: [Atari Jaguar, developerSupport, limited third-party support]
-
A.
digitalSupport
Indicates that one entity provides assistance, resources, or services to another through digital or online means.
-
B.
developerStudio
Indicates that a software developer or development team is associated with, works at, or uses a particular development studio or integrated development environment (IDE).
-
C.
softwareHelpPage
Indicates that a software application provides a dedicated help or support page for users.
-
D.
developmentPillar
Indicates that one entity serves as a fundamental pillar or core focus area supporting the development or growth of another entity.
-
E.
platformIssue
Indicates that there is a problem, malfunction, or limitation affecting the operation or availability of a platform.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e989fdac81909a4a75f1f68b55c6 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.