Triple
T9030229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMPTE color bars |
E216148
|
entity |
| Predicate | outputBy |
P66288
|
FINISHED |
| Object | professional video cameras |
—
|
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: professional video cameras | Statement: [SMPTE color bars, outputBy, professional video cameras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputBy Context triple: [SMPTE color bars, outputBy, professional video cameras]
-
A.
outputOf
chosen
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
B.
outputsTo
Indicates that the result or data produced by one entity is directed or sent to another entity as its destination or target.
-
C.
outputUsedBy
Indicates that a particular output produced by one entity is consumed, referenced, or otherwise utilized by another entity.
-
D.
outputProperty
Indicates that a property or attribute is produced, exposed, or yielded as the output of a process, function, or system.
-
E.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9e0aa881908886f453c51ecd0e |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.