Triple
T25086149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Béatrice de Rothschild |
E628327
|
entity |
| Predicate | designedGardensWith |
P19613
|
FINISHED |
| Object | landscape architects |
—
|
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: landscape architects | Statement: [Béatrice de Rothschild, designedGardensWith, landscape architects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedGardensWith Context triple: [Béatrice de Rothschild, designedGardensWith, landscape architects]
-
A.
landscapeDesignedBy
chosen
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
B.
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.
-
C.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
D.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
E.
createdAsGarden
Indicates that something was brought into existence or established specifically in the form or function of 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 6:23 a.m.