Triple
T32972945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt series |
E843573
|
entity |
| Predicate | operationalStartPeriod |
P202035
|
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: [Thunderbolt series, operationalStartPeriod, early 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStartPeriod Context triple: [Thunderbolt series, operationalStartPeriod, early 1940s]
-
A.
programStartPeriod
Indicates the time interval during which a program is initially scheduled to begin or become active.
-
B.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
C.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
D.
testPeriodStart
Indicates the date or time at which a specified test or testing period begins.
-
E.
operatorStart
Indicates the point in time or event at which an operator begins performing an action or process.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_6a004868cf308190a2a93c32c92f22d9 |
completed | May 10, 2026, 8:57 a.m. |
Created at: May 1, 2026, 1:22 a.m.