Triple
T11881502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Parterre |
E282667
|
entity |
| Predicate | hasLayoutElement |
P102036
|
FINISHED |
| Object | parterre de broderie |
—
|
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: parterre de broderie | Statement: [Great Parterre, hasLayoutElement, parterre de broderie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayoutElement Context triple: [Great Parterre, hasLayoutElement, parterre de broderie]
-
A.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
B.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
C.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
D.
hasExhibitElement
Indicates that something (such as an exhibit or display) includes or is composed of a particular element or component.
-
E.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
- F. None of above. chosen
Provenance (4 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.