Triple
T20165308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NES Zapper |
E491811
|
entity |
| Predicate | requiresDisplayType |
P138915
|
FINISHED |
| Object | CRT television |
—
|
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: CRT television | Statement: [NES Zapper, requiresDisplayType, CRT television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDisplayType Context triple: [NES Zapper, requiresDisplayType, CRT television]
-
A.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
B.
displayType
Indicates the manner or format in which something is presented, shown, or rendered.
-
C.
requiresShowing
Indicates that one entity must be displayed or made visible as a prerequisite or condition for another entity, action, or state.
-
D.
requiresShowingBy
Indicates that one entity must be demonstrated, displayed, or presented by another entity as a necessary condition or step.
-
E.
displaysFeature
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:35 p.m.