Triple
T4771218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertzian waves |
E105930
|
entity |
| Predicate | firstDemonstratedIn |
P1588
|
FINISHED |
| Object | 1887 |
—
|
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: 1887 | Statement: [Hertzian waves, firstDemonstratedIn, 1887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDemonstratedIn Context triple: [Hertzian waves, firstDemonstratedIn, 1887]
-
A.
firstDemonstrated
chosen
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
B.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
C.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
D.
firstDeployedIn
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
-
E.
wasFirstObservedIn
Indicates that an entity was initially noticed, recorded, or detected at a particular time or place.
- 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.