Triple
T2032963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Photophone |
E44558
|
entity |
| Predicate | signalCarrier |
P4618
|
FINISHED |
| Object | visible light |
—
|
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: visible light | Statement: [Photophone, signalCarrier, visible light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalCarrier Context triple: [Photophone, signalCarrier, visible light]
-
A.
soundCarrier
Indicates that one entity serves as a medium or object that carries, stores, or transmits sound for another entity.
-
B.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
C.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
D.
militarySignal
Indicates a relationship where one party sends or uses a signal for military or defense-related purposes toward another party or target.
-
E.
signallingSystem
Indicates that one entity functions as a signalling system used to transmit information or cues to another entity.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.