Triple
T25342681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tissington |
E635457
|
entity |
| Predicate | estateOwnedBy |
P110318
|
FINISHED |
| Object | FitzHerbert family |
—
|
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: FitzHerbert family | Statement: [Tissington, estateOwnedBy, FitzHerbert family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estateOwnedBy Context triple: [Tissington, estateOwnedBy, FitzHerbert family]
-
A.
ownsPropertyIn
Indicates that one entity possesses legal ownership rights over property located within a specified place or jurisdiction.
-
B.
estateRole
Indicates the specific function, capacity, or responsibility an entity holds in relation to an estate (such as owner, executor, or beneficiary).
-
C.
ownedResidence
chosen
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
D.
estateManaged
Indicates that one entity is responsible for administering, overseeing, or handling the affairs and assets of another entity’s estate.
-
E.
ownerOccupation
Indicates that the occupation or job role of an entity that owns something is being specified or described.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b936f08190b750199798e9effc |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:32 p.m.