Triple
T27381530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat G.82 |
E691243
|
entity |
| Predicate | originatesFromDesignLine |
P36679
|
FINISHED |
| Object | Fiat G-series aircraft |
E691243
|
NE 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: Fiat G-series aircraft | Statement: [Fiat G.82, originatesFromDesignLine, Fiat G-series aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromDesignLine Context triple: [Fiat G.82, originatesFromDesignLine, Fiat G-series aircraft]
-
A.
hasDesignOrigin
chosen
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
B.
hasOriginalLineDesignation
Indicates that an entity is associated with its initial or historically assigned line designation before any subsequent changes or renamings.
-
C.
basedOnDesignBy
Indicates that something is created, developed, or structured according to the design conceived or produced by a specified entity.
-
D.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
E.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
- F. None of above.
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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12a7ec1ba8819098c921f65a26212c |
completed | May 24, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 27, 2026, 12:22 p.m.