Triple
T23774813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune Fountain (Boboli Gardens) |
E587638
|
entity |
| Predicate | gardenTypeContext |
P12538
|
FINISHED |
| Object | Italian formal garden |
—
|
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: Italian formal garden | Statement: [Neptune Fountain (Boboli Gardens), gardenTypeContext, Italian formal garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardenTypeContext Context triple: [Neptune Fountain (Boboli Gardens), gardenTypeContext, Italian formal garden]
-
A.
hasGardenType
chosen
Indicates that an entity possesses or is associated with a garden of a specified type.
-
B.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
-
C.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
D.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
E.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
- 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.