Triple
T3740565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System M |
E79686
|
entity |
| Predicate | fieldFrequency |
P85
|
FINISHED |
| Object | 59.94 Hz in color NTSC implementations |
—
|
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: 59.94 Hz in color NTSC implementations | Statement: [System M, fieldFrequency, 59.94 Hz in color NTSC implementations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldFrequency Context triple: [System M, fieldFrequency, 59.94 Hz in color NTSC implementations]
-
A.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
B.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
C.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
D.
fieldPattern
Indicates a recurring or structured arrangement or configuration present within a field or area.
-
E.
frequencyCategory
Indicates how often an action, event, or relationship occurs, typically by assigning it to a qualitative frequency level (e.g., rare, occasional, frequent).
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb5344fc8190b183aca5c04e3bcc |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.