Triple
T2736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee de Forest |
E51
|
entity |
| Predicate | doctoralThesisTopic |
P3
|
FINISHED |
| Object | radio waves |
—
|
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: radio waves | Statement: [Lee de Forest, doctoralThesisTopic, radio waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctoralThesisTopic Context triple: [Lee de Forest, doctoralThesisTopic, radio waves]
-
A.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
B.
fieldOfWork
chosen
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
academicDegree
Indicates that an entity holds or has been awarded a specific academic degree.
-
E.
academicStructure
Indicates a hierarchical or organizational relationship within an academic system, such as how programs, departments, courses, or degrees are structured and related to one another.
- 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_69a22e0d37588190897cf37a323013f5 |
completed | Feb. 27, 2026, 11:51 p.m. |
| NER | Named-entity recognition | batch_69a2316d88a08190b2e03041674b5674 |
completed | Feb. 28, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69a230c3ee4481908216244c38aa8aef |
completed | Feb. 28, 2026, 12:03 a.m. |
Created at: Feb. 27, 2026, 11:55 p.m.