Triple
T23541127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leslie, Aberdeenshire |
E577749
|
entity |
| Predicate | hasAncestralEstateOf |
P90583
|
FINISHED |
| Object | Clan Leslie |
—
|
NE NERFINISHED |
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: Clan Leslie | Statement: [Leslie, Aberdeenshire, hasAncestralEstateOf, Clan Leslie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralEstateOf Context triple: [Leslie, Aberdeenshire, hasAncestralEstateOf, Clan Leslie]
-
A.
hasAncestralLand
chosen
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
B.
hasAncestralResidence
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
C.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
D.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
E.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1b3a8c8190b5b6a58f0476c5d2 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.