Triple
T1072789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macchi C.205 Veltro |
E23366
|
entity |
| Predicate | engineOrigin |
P17328
|
FINISHED |
| Object | license-built Daimler-Benz DB 605 |
—
|
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: license-built Daimler-Benz DB 605 | Statement: [Macchi C.205 Veltro, engineOrigin, license-built Daimler-Benz DB 605]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineOrigin Context triple: [Macchi C.205 Veltro, engineOrigin, license-built Daimler-Benz DB 605]
-
A.
engineSupplier
chosen
Indicates a relationship where one entity supplies or provides engines to another entity.
-
B.
originallyBuiltBy
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
C.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
D.
manufacturedBy
Indicates that an item or product is produced or created by a specific manufacturer or maker.
-
E.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92afad88190b7705923f71fc760 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.