Triple
T1468565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caproni Ca.135 |
E27080
|
entity |
| Predicate | designedInPeriod |
P1578
|
FINISHED |
| Object | interwar period |
—
|
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: interwar period | Statement: [Caproni Ca.135, designedInPeriod, interwar period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedInPeriod Context triple: [Caproni Ca.135, designedInPeriod, interwar period]
-
A.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
B.
designedIn
chosen
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
C.
designPeriod
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
D.
hasDesignPeriod
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
E.
partOfCreativePeriod
Indicates that one creative work, phase, or output belongs to or occurs within a broader creative period or movement.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5d70a948190b50a6c1b36abc740 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.