Triple
T18730749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maserati Alfieri |
E458027
|
entity |
| Predicate | designDirector |
P28525
|
FINISHED |
| Object | Lorenzo Ramaciotti |
—
|
NE NERFINISHED |
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: Lorenzo Ramaciotti | Statement: [Maserati Alfieri, designDirector, Lorenzo Ramaciotti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designDirector Context triple: [Maserati Alfieri, designDirector, Lorenzo Ramaciotti]
-
A.
designLead
chosen
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
B.
designConsultant
Indicates that one entity serves as a design consultant, providing expert design advice or services, to another entity.
-
C.
designBureau
Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
-
D.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
E.
designSucceededBy
Indicates that one design is followed or replaced by another design in a temporal or version sequence.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d778cf8819083500600b9ac0744 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:50 a.m.