Triple
T15756462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Düppel |
E381978
|
entity |
| Predicate | introducedApproximateTime |
P56255
|
FINISHED |
| Object | early 1940s |
—
|
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 1940s | Statement: [Düppel, introducedApproximateTime, early 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedApproximateTime Context triple: [Düppel, introducedApproximateTime, early 1940s]
-
A.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
B.
initialReleaseApprox
chosen
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
-
C.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
D.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
E.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b1ff4881909d5240d1d30f5c8b |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.