Triple
T28461968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Mary Ashley-Cooper |
E720177
|
entity |
| Predicate | hasAncestralSeatAssociated |
P64286
|
FINISHED |
| Object | Shaftesbury |
—
|
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: Shaftesbury | Statement: [Lady Mary Ashley-Cooper, hasAncestralSeatAssociated, Shaftesbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralSeatAssociated Context triple: [Lady Mary Ashley-Cooper, hasAncestralSeatAssociated, Shaftesbury]
-
A.
hasHistoricalSeat
chosen
Indicates that an entity possesses or is associated with a historically significant seat, location, or place of authority.
-
B.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
C.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
D.
hasAncestralLand
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
E.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 2:41 a.m.