Triple
T35283765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F.22 Pinguino |
E1019013
|
entity |
| Predicate | designerReputation |
P57360
|
FINISHED |
| Object | renowned aircraft designer |
—
|
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: renowned aircraft designer | Statement: [F.22 Pinguino, designerReputation, renowned aircraft designer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designerReputation Context triple: [F.22 Pinguino, designerReputation, renowned aircraft designer]
-
A.
designReputation
chosen
Indicates the perceived quality or standing of an entity based on others’ judgments of its design.
-
B.
fashionReputation
Indicates the perceived status or esteem an entity holds within the context of fashion, based on how its style, taste, or influence is judged by others.
-
C.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
D.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
E.
reputationHub
Indicates a central entity that aggregates, manages, or influences the reputations of multiple other entities.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:03 p.m.