Triple
T30281657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spencer-Stanhope |
E770109
|
entity |
| Predicate | familySeatLocatedIn |
P32085
|
FINISHED |
| Object | Cawthorne, Yorkshire |
—
|
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: Cawthorne, Yorkshire | Statement: [Spencer-Stanhope, familySeatLocatedIn, Cawthorne, Yorkshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familySeatLocatedIn Context triple: [Spencer-Stanhope, familySeatLocatedIn, Cawthorne, Yorkshire]
-
A.
seatLocatedIn
Indicates that a seat is situated within or belongs to a specific location or area.
-
B.
seatLocatedAt
Indicates that a seat is positioned or situated at a specific location or place.
-
C.
familySeatFunction
Indicates that a location serves as the principal seat, residence, or base associated with a particular family or lineage.
-
D.
familySeatRegion
chosen
Indicates the region in which a family's principal seat, base, or ancestral home is located.
-
E.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 7:45 p.m.