Triple
T8437536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 162 |
E199265
|
entity |
| Predicate | developmentTime |
P83363
|
FINISHED |
| Object | about 3 months from design to prototype |
—
|
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: about 3 months from design to prototype | Statement: [Heinkel He 162, developmentTime, about 3 months from design to prototype]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentTime Context triple: [Heinkel He 162, developmentTime, about 3 months from design to prototype]
-
A.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
B.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
C.
mainDevelopmentPeriod
Indicates the primary time span during which the main development or formation of something took place.
-
D.
developmentPillar
Indicates that one entity serves as a fundamental pillar or core focus area supporting the development or growth of another entity.
-
E.
developmentMethod
Indicates the process, technique, or approach used to create, build, or evolve something.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:08 p.m.