Triple
T30369783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SECAM |
E772517
|
entity |
| Predicate | colorEncodingSystem |
P62473
|
FINISHED |
| Object | frequency modulation of color subcarrier |
—
|
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: frequency modulation of color subcarrier | Statement: [SECAM, colorEncodingSystem, frequency modulation of color subcarrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorEncodingSystem Context triple: [SECAM, colorEncodingSystem, frequency modulation of color subcarrier]
-
A.
colorEncoding
Indicates how the color information of an entity is represented, formatted, or encoded.
-
B.
colorEncodingMethod
Indicates the method or scheme used to represent or encode color information.
-
C.
colorSystem
chosen
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
D.
colourSystemComponent
Indicates that one entity is a component or part of a colour system associated with another entity.
-
E.
colorSystemCompatibleWith
Indicates that one color system can be accurately used, interpreted, or converted within the context of another color system without loss of intended color meaning.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 7:59 p.m.