Triple
T15434264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van de Graaff generator |
E369717
|
entity |
| Predicate | developmentDate |
P118762
|
FINISHED |
| Object | early 1930s |
—
|
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: early 1930s | Statement: [Van de Graaff generator, developmentDate, early 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentDate Context triple: [Van de Graaff generator, developmentDate, early 1930s]
-
A.
developedAt
Indicates the place or location where something was created, built, or developed.
-
B.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
C.
dateImplemented
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
-
D.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
E.
yearOfDevelopment
Indicates the specific year in which something was developed or created.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edb3ec481908b26164d4470c9bc |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.