Triple
T35483470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat G.91 |
E1025527
|
entity |
| Predicate | namedAfterDesignerInitials |
P55530
|
FINISHED |
| Object | G. for Gabrielli |
—
|
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: G. for Gabrielli | Statement: [Fiat G.91, namedAfterDesignerInitials, G. for Gabrielli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterDesignerInitials Context triple: [Fiat G.91, namedAfterDesignerInitials, G. for Gabrielli]
-
A.
designerInitials
chosen
Indicates that the associated value is the set of initials of the designer involved in the described entity or action.
-
B.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
C.
formerNameOfDesigner
Indicates that one entity was previously the name used by a designer before being changed to a new name.
-
D.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
E.
designBureauNamedAfter
Indicates that a design bureau is named in honor of or after a particular person, organization, or 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:04 p.m.