Triple
T2548354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowood House park |
E57958
|
entity |
| Predicate | eraOfDesign |
P14116
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Bowood House park, eraOfDesign, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfDesign Context triple: [Bowood House park, eraOfDesign, 18th century]
-
A.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
B.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
C.
eraOfSignificance
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
-
D.
hasDesignPeriod
chosen
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
E.
eraOfConversion
Indicates the specific historical period or era during which the conversion event or change took place.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2e7cd4c8190a52cbbf1229441a6 |
completed | March 7, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.