Triple
T23774682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viottolone avenue |
E587634
|
entity |
| Predicate | hasTypeOfDesign |
P1529
|
FINISHED |
| Object | formal garden axis |
—
|
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: formal garden axis | Statement: [Viottolone avenue, hasTypeOfDesign, formal garden axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDesign Context triple: [Viottolone avenue, hasTypeOfDesign, formal garden axis]
-
A.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
C.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
D.
hasDesigned
Indicates that one entity is the creator or designer of another entity.
-
E.
hasDesignInputFrom
Indicates that the design of one entity is based on, influenced by, or derived from input provided by another 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c46a19688190aa91f1f10ba5c4ee |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.