Triple
T11509455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 1 |
E272869
|
entity |
| Predicate | televisionSystemType |
P99866
|
FINISHED |
| Object | vidicon-based TV camera |
—
|
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: vidicon-based TV camera | Statement: [Surveyor 1, televisionSystemType, vidicon-based TV camera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: televisionSystemType Context triple: [Surveyor 1, televisionSystemType, vidicon-based TV camera]
-
A.
televisionFormat
Indicates the specific type or style of television program or production format associated with an entity.
-
B.
televisionPlatform
Indicates that one entity serves as the television platform (e.g., service, system, or distribution channel) through which the other entity’s TV content is delivered or accessed.
-
C.
televisionNetworkAssociation
Indicates a relationship where an entity is affiliated with, carried by, or part of a particular television network.
-
D.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
E.
televisionServiceStatus
Indicates the operational or subscription state of a television service for an entity.
- F. None of above. chosen
Provenance (4 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db65eb081908613a1002c6a4fb4 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.