Triple
T5623413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna 3 |
E147661
|
entity |
| Predicate | dataTransmissionMethod |
P5991
|
FINISHED |
| Object | analog television scan of developed film |
—
|
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: analog television scan of developed film | Statement: [Luna 3, dataTransmissionMethod, analog television scan of developed film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTransmissionMethod Context triple: [Luna 3, dataTransmissionMethod, analog television scan of developed film]
-
A.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
B.
baseTransmission
Indicates the fundamental or default mode by which something is transmitted or passed from one entity to another.
-
C.
attachmentMethod
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
-
D.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
E.
dataTransferType
chosen
Indicates the method or mode by which data is transmitted or exchanged between entities.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02214b4948190b71a9f59499092f6 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.