Triple
T37009022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariner 6 |
E915888
|
entity |
| Predicate | primaryImagingInstrument |
P53868
|
FINISHED |
| Object | television camera system |
—
|
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: television camera system | Statement: [Mariner 6, primaryImagingInstrument, television camera system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryImagingInstrument Context triple: [Mariner 6, primaryImagingInstrument, television camera system]
-
A.
imagingInstrument
chosen
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
B.
observingInstrument
Indicates that one entity serves as the instrument or device used by another entity to perform an observation.
-
C.
usesPrimaryBeam
Indicates that one entity employs another entity as its main or principal beam in an operation or structure.
-
D.
spectralInstrumentType
Indicates the type or category of instrument used to acquire spectral measurements in the described relationship or observation.
-
E.
primaryDetectorType
Indicates the main kind or category of detector that is used as the primary sensing or measurement component in a given context.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.