Triple
T4771215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertzian waves |
E105930
|
entity |
| Predicate | confirmedTheoryOf |
P58681
|
FINISHED |
| Object | electromagnetism |
—
|
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: electromagnetism | Statement: [Hertzian waves, confirmedTheoryOf, electromagnetism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedTheoryOf Context triple: [Hertzian waves, confirmedTheoryOf, electromagnetism]
-
A.
supportsTheory
Indicates that one entity provides evidence, justification, or endorsement for the validity or acceptance of another entity’s theory.
-
B.
confirmedPredictionOf
Indicates that a previously made prediction about an entity or event has been verified as accurate or true.
-
C.
contradictedTheory
Indicates that one entity has presented evidence, arguments, or findings that oppose, challenge, or invalidate the theory proposed by another entity.
-
D.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
E.
occursInTheory
Indicates that an event, concept, or phenomenon is situated, described, or analyzed within a particular theoretical framework or theory.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655e5dcc8190a932be9b1baaffb2 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:21 p.m.