Triple
T35340683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balloch Castle Country Park |
E1020586
|
entity |
| Predicate | mainBuildingConstructionCentury |
P6333
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Balloch Castle Country Park, mainBuildingConstructionCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBuildingConstructionCentury Context triple: [Balloch Castle Country Park, mainBuildingConstructionCentury, 19th century]
-
A.
constructionCentury
chosen
Indicates the century during which something was constructed or built.
-
B.
containsBuildingFromCentury
Indicates that a location or area includes at least one building that originates from a specified century.
-
C.
estimatedConstructionEndCentury
Indicates the century in which the construction of something is estimated to have been completed.
-
D.
originalBuildingDemolishedInCentury
Indicates that the original building was demolished at some point during the specified century.
-
E.
locatedInBuildingConstructedInCentury
Indicates that something is located in a building whose construction dates to a specified century.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.