Triple
T31818837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wien bridge oscillator |
E812208
|
entity |
| Predicate | yearOfFirstImplementation |
P90584
|
FINISHED |
| Object | 1939 |
—
|
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: 1939 | Statement: [Wien bridge oscillator, yearOfFirstImplementation, 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfFirstImplementation Context triple: [Wien bridge oscillator, yearOfFirstImplementation, 1939]
-
A.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
B.
firstPublicUseYear
Indicates the calendar year in which something was first made available for use by the public.
-
C.
dateImplemented
chosen
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
-
D.
yearOfDevelopment
Indicates the specific year in which something was developed or created.
-
E.
introducedInPublicationYear
Indicates the year in which something (such as a concept, method, or product) was first introduced or presented in a publication.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 30, 2026, 11:45 p.m.