Triple
T634374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTSC color television standard |
E15990
|
entity |
| Predicate | audioCarrierOffset |
P3510
|
FINISHED |
| Object | 4.5 MHz above video carrier |
—
|
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: 4.5 MHz above video carrier | Statement: [NTSC color television standard, audioCarrierOffset, 4.5 MHz above video carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioCarrierOffset Context triple: [NTSC color television standard, audioCarrierOffset, 4.5 MHz above video carrier]
-
A.
soundCarrier
chosen
Indicates that one entity serves as a medium or object that carries, stores, or transmits sound for another entity.
-
B.
offsets
Indicates that one entity counterbalances, compensates for, or reduces the effect, value, or impact of another.
-
C.
timeOffsetReference
Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
-
D.
offsetSeconds
Indicates a temporal relationship where one event or time point occurs a specified number of seconds before or after another reference time.
-
E.
usesOffsetFrom
Indicates that one entity determines or expresses its position, value, or behavior relative to another by applying a specified offset from that reference.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee4ee8481908ad45405e3f3835c |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d0483908190a5ec42a7403c258e |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.