Triple
T29949119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATI Flipper |
E760720
|
entity |
| Predicate | outputResolution |
P5732
|
FINISHED |
| Object | 480i |
—
|
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: 480i | Statement: [ATI Flipper, outputResolution, 480i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputResolution Context triple: [ATI Flipper, outputResolution, 480i]
-
A.
displayResolution
chosen
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
B.
targetResolution
Indicates the specific resolution or level of detail that an action, process, or system is intended to achieve or operate at.
-
C.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
-
D.
sensorResolution
Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
-
E.
printingResolution
Indicates the level of detail or clarity at which something is printed, typically measured as resolution (e.g., dots per inch).
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6780dd5d08190b1ef4e49405a5419 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:25 p.m.