Triple
T6641512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privy Garden |
E150595
|
entity |
| Predicate | plantingScheme |
P9738
|
FINISHED |
| Object | formal bedding with clipped hedges |
—
|
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 bedding with clipped hedges | Statement: [Privy Garden, plantingScheme, formal bedding with clipped hedges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantingScheme Context triple: [Privy Garden, plantingScheme, formal bedding with clipped hedges]
-
A.
plantingStyle
chosen
Indicates the method or arrangement used to plant entities in relation to each other or their environment.
-
B.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
C.
plantArea
Indicates the total surface area occupied or covered by a plant or group of plants.
-
D.
plantCollection
Indicates that one entity maintains or possesses a collection of plants, typically grouped or curated as a set.
-
E.
fieldDesign
Indicates a relationship where an entity is responsible for planning, arranging, or specifying the layout and structure of a particular field or area.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 2 p.m.