Triple
T2032945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Photophone |
E44558
|
entity |
| Predicate | communicationPrinciple |
P35428
|
FINISHED |
| Object | modulation of light intensity by sound |
—
|
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: modulation of light intensity by sound | Statement: [Photophone, communicationPrinciple, modulation of light intensity by sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationPrinciple Context triple: [Photophone, communicationPrinciple, modulation of light intensity by sound]
-
A.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
B.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
C.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
D.
communicationRule
Indicates a rule or constraint that governs how communication between entities should occur.
-
E.
communicationModelRole
Indicates the role an entity plays within a communication model, specifying its function or position in the communication process.
- 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_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. |
| PDg | Predicate description generation | batch_69abb90ec7948190bbfb0329e9e67cca |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:39 p.m.