Triple
T30868828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansion of Bahjí complex |
E786278
|
entity |
| Predicate | gardensDesign |
P54626
|
FINISHED |
| Object | formal ornamental 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: formal ornamental gardens | Statement: [Mansion of Bahjí complex, gardensDesign, formal ornamental gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardensDesign Context triple: [Mansion of Bahjí complex, gardensDesign, formal ornamental gardens]
-
A.
gardensStyle
chosen
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
B.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
C.
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.
-
D.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
-
E.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:47 p.m.