Triple
T19661335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baird television camera |
E472087
|
entity |
| Predicate | scanDevice |
P49003
|
FINISHED |
| Object | spinning perforated disk |
—
|
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: spinning perforated disk | Statement: [Baird television camera, scanDevice, spinning perforated disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scanDevice Context triple: [Baird television camera, scanDevice, spinning perforated disk]
-
A.
scanType
Indicates the specific kind or category of scanning operation performed or required in a given context.
-
B.
scans
chosen
Indicates performing a systematic examination or inspection of something, often using a device or method to detect, read, or analyze its contents or structure.
-
C.
hasScanningCenter
Indicates that an entity is associated with, or makes use of, a particular scanning center for scanning-related activities.
-
D.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
E.
usesScanningMethod
Indicates that an entity performs or carries out an action by employing a specific scanning method.
- 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.