Triple
T37731094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croome Park |
E940155
|
entity |
| Predicate | landscapeDesignEndDate |
P2286
|
FINISHED |
| Object | c. 1770s |
—
|
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: c. 1770s | Statement: [Croome Park, landscapeDesignEndDate, c. 1770s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landscapeDesignEndDate Context triple: [Croome Park, landscapeDesignEndDate, c. 1770s]
-
A.
paintingCompletionDate
Indicates the date on which a painting was finished or completed.
-
B.
designDate
chosen
Indicates the date on which something was originally designed or its design was completed.
-
C.
laterDamCompletionDate
Indicates that one dam’s completion date occurs chronologically after another dam’s completion date.
-
D.
designPeriod
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
E.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
- 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_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.