Triple
T30483798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMPTE ST 2094 |
E775658
|
entity |
| Predicate | componentStandard |
P121725
|
FINISHED |
| Object | SMPTE ST 2094-1 |
—
|
NE NERFINISHED |
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: SMPTE ST 2094-1 | Statement: [SMPTE ST 2094, componentStandard, SMPTE ST 2094-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentStandard Context triple: [SMPTE ST 2094, componentStandard, SMPTE ST 2094-1]
-
A.
componentStandardization
chosen
Indicates that one entity is standardized, normalized, or made uniform according to the specifications, rules, or format defined by another entity.
-
B.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
C.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
-
D.
componentCC
Indicates that one entity is a component or constituent part of another entity within a coordinated or composite construction.
-
E.
componentPractice
Indicates that one entity is a specific practice, method, or procedure that functions as a component or sub-practice within another, broader practice 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 8:13 p.m.