Triple
T8483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | superheterodyne receiver |
E169
|
entity |
| Predicate | wasInventedInYear |
P633
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [superheterodyne receiver, wasInventedInYear, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInventedInYear Context triple: [superheterodyne receiver, wasInventedInYear, 1918]
-
A.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
B.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
C.
developedAt
Indicates the place or location where something was created, built, or developed.
-
D.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
E.
yearSigned
Indicates the specific year in which an agreement, contract, or document was formally signed.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a2407916ac8190b76d2e6690efaef3 |
completed | Feb. 28, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69a23fe3a87881909ab95bb3a0b474ec |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a240782e108190b6b60c26b84ae179 |
completed | Feb. 28, 2026, 1:10 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.