Triple
T8472482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Original Amiga chipset |
E200310
|
entity |
| Predicate | videoStandardsSupported |
P76289
|
FINISHED |
| Object | PAL |
—
|
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: PAL | Statement: [Original Amiga chipset, videoStandardsSupported, PAL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoStandardsSupported Context triple: [Original Amiga chipset, videoStandardsSupported, PAL]
-
A.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
-
B.
supportsDisplayStandard
chosen
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
C.
televisionFormat
Indicates the specific type or style of television program or production format associated with an entity.
-
D.
digitalStandard
Indicates that one entity defines, specifies, or embodies a recognized digital standard that the other entity follows, implements, or is evaluated against.
-
E.
supportsHEVC
Indicates that one entity provides compatibility with or the ability to handle HEVC (High Efficiency Video Coding) 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.