Triple
T17241211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballindalloch Castle |
E418501
|
entity |
| Predicate | continuousFamilyOwnership |
P116530
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ballindalloch Castle, continuousFamilyOwnership, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousFamilyOwnership Context triple: [Ballindalloch Castle, continuousFamilyOwnership, true]
-
A.
multiGenerationOwnershipOf
Indicates that ownership of something extends across multiple generations within the same family or lineage.
-
B.
heldByFamilySince
chosen
Indicates that something has been continuously possessed or owned by the same family from a certain point in time.
-
C.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
D.
relatedFamilyBusiness
Indicates that there is a connection between entities through ownership, management, or involvement in the same family-run business or businesses.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e203ec88190a21f38cbb18a14fa |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.