Triple
T19661355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baird television camera |
E472087
|
entity |
| Predicate | mediaTypeCaptured |
P21736
|
FINISHED |
| Object | live studio scenes |
—
|
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: live studio scenes | Statement: [Baird television camera, mediaTypeCaptured, live studio scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaTypeCaptured Context triple: [Baird television camera, mediaTypeCaptured, live studio scenes]
-
A.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
B.
mediaTypeRecognized
Indicates that a system has successfully identified and accepted the type or format of a given media item as valid or supported.
-
C.
mediaTypeExample
Indicates that something serves as an example or illustrative instance of a particular media type.
-
D.
mediaTypeAvailable
Indicates that a particular type or format of media is available for use, access, or distribution in the given context.
-
E.
captureType
chosen
Indicates the manner or method by which something is captured, recorded, or acquired in the context of the relationship.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414a667c81909aad04a737773c7e |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.