Triple
T37731093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croome Park |
E940155
|
entity |
| Predicate | landscapeDesignStartDate |
P102750
|
FINISHED |
| Object | 1751 |
—
|
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: 1751 | Statement: [Croome Park, landscapeDesignStartDate, 1751]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landscapeDesignStartDate Context triple: [Croome Park, landscapeDesignStartDate, 1751]
-
A.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
B.
designStarted
chosen
Indicates that the process of designing something has been initiated or begun.
-
C.
hasLandscaping
Indicates that an entity possesses or is associated with designed outdoor grounds or landscape features.
-
D.
landscapeManagement
Indicates the planning, implementation, and maintenance of actions that shape, conserve, or restore the physical and ecological characteristics of a landscape.
-
E.
designDate
Indicates the date on which something was originally designed or its design was completed.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.