Triple
T4771234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertzian waves |
E105930
|
entity |
| Predicate | detectedBy |
P28555
|
FINISHED |
| Object | loop antenna with spark gap |
—
|
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: loop antenna with spark gap | Statement: [Hertzian waves, detectedBy, loop antenna with spark gap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectedBy Context triple: [Hertzian waves, detectedBy, loop antenna with spark gap]
-
A.
detected
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
B.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
C.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
D.
usedInDetector
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
-
E.
discoveredWith
chosen
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
- 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_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. |
Created at: March 20, 2026, 1:21 p.m.