Triple
T634371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTSC color television standard |
E15990
|
entity |
| Predicate | fieldRate |
P85
|
FINISHED |
| Object | 59.94 fields per second |
—
|
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 fields per second | Statement: [NTSC color television standard, fieldRate, 59.94 fields per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldRate Context triple: [NTSC color television standard, fieldRate, 59.94 fields per second]
-
A.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
fieldQuality
Indicates the assessed level or degree of quality associated with a particular field or attribute in a given context.
-
C.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
D.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
E.
fieldCovered
Indicates that a specified field or area is physically or functionally covered by some material, object, or condition.
- 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.