Triple
T30369838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SECAM |
E772517
|
entity |
| Predicate | videoStandardFamily |
P79874
|
FINISHED |
| Object | 625/50 analog television systems |
—
|
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: 625/50 analog television systems | Statement: [SECAM, videoStandardFamily, 625/50 analog television systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoStandardFamily Context triple: [SECAM, videoStandardFamily, 625/50 analog television systems]
-
A.
videoStandard
chosen
Indicates the video format or broadcasting standard that applies to a given video or recording.
-
B.
televisionFormat
Indicates the specific type or style of television program or production format associated with an entity.
-
C.
digitalStandard
Indicates that one entity defines, specifies, or embodies a recognized digital standard that the other entity follows, implements, or is evaluated against.
-
D.
standardDefinition
Indicates that something serves as the officially accepted or commonly recognized definition of a term or concept.
-
E.
homeVideo
Indicates that an entity is a video recording made in a domestic or personal setting, typically by non-professionals for private use.
- 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_69f682836d308190b22a0efc893e7a45 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:59 p.m.