Triple
T7070572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château de Villandry |
E164680
|
entity |
| Predicate | gardenLayout |
P54626
|
FINISHED |
| Object | formal French 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: formal French garden | Statement: [Château de Villandry, gardenLayout, formal French garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardenLayout Context triple: [Château de Villandry, gardenLayout, formal French garden]
-
A.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
B.
gardensStyle
chosen
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
C.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
D.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4c862f481908d1faf6ed57774f1 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.