Triple
T32767528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigli of Milan |
E837941
|
entity |
| Predicate | partiallyDesignedBy |
P184
|
FINISHED |
| Object | Leonardo da Vinci |
—
|
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: Leonardo da Vinci | Statement: [Navigli of Milan, partiallyDesignedBy, Leonardo da Vinci]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyDesignedBy Context triple: [Navigli of Milan, partiallyDesignedBy, Leonardo da Vinci]
-
A.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
B.
designedAsPartOfSystemBy
Indicates that an entity was intentionally created as a component or module within a larger system by a specific designer or designing agent.
-
C.
partiallyComposedBy
Indicates that one entity is made up in part, but not entirely, of another entity or set of entities.
-
D.
hasPartInHisDesign
Indicates that one entity is included as a component or element within the design or plan created by another entity.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:13 a.m.