Triple
T9000986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEC aperture grille CRTs |
E215036
|
entity |
| Predicate | intendedSignalType |
P4618
|
FINISHED |
| Object | analog video signal |
—
|
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: analog video signal | Statement: [NEC aperture grille CRTs, intendedSignalType, analog video signal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedSignalType Context triple: [NEC aperture grille CRTs, intendedSignalType, analog video signal]
-
A.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
searchesSignalType
Indicates that an entity actively looks for or queries a specific type or category of signal.
-
C.
intendedReceiver
Indicates that one entity is the target or designated recipient of something (such as a message, item, or action) originating from another entity.
-
D.
compatibleWithSignaling
Indicates that one entity can correctly interpret, process, or operate using the signaling mechanisms, protocols, or formats employed by another entity.
-
E.
specType
Indicates the specific type or category of a specification that an entity is associated with.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6954bb1881908d004a26ba7fe360 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.