Triple
T33358108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers Ju 60 |
E854129
|
entity |
| Predicate | designImprovedIn |
P161052
|
FINISHED |
| Object | Junkers Ju 160 |
—
|
NE NERFINISHED |
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: Junkers Ju 160 | Statement: [Junkers Ju 60, designImprovedIn, Junkers Ju 160]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designImprovedIn Context triple: [Junkers Ju 60, designImprovedIn, Junkers Ju 160]
-
A.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
B.
improvesIn
chosen
Indicates that one entity causes or contributes to an increase in quality, performance, or effectiveness in another entity or context.
-
C.
designSimplification
Indicates a relationship where one entity reduces the complexity of another entity’s design, making it simpler or more streamlined.
-
D.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
-
E.
designStandardizedIn
Indicates that something is designed according to the rules, formats, or specifications defined within a particular standard or standardization framework.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 1:34 a.m.