Triple
T37895144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Street (Edinburgh) |
E945254
|
entity |
| Predicate | gardensType |
P12538
|
FINISHED |
| Object | private communal gardens |
—
|
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: private communal gardens | Statement: [Queen Street (Edinburgh), gardensType, private communal gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardensType Context triple: [Queen Street (Edinburgh), gardensType, private communal gardens]
-
A.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
B.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
C.
hasGardenType
chosen
Indicates that an entity possesses or is associated with a garden of a specified type.
-
D.
gardensBuiltFor
Indicates that one entity (such as a garden or landscaped area) was created or designed specifically for the benefit, use, or purpose of another entity.
-
E.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.