Triple
T27990277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warter, East Riding of Yorkshire |
E706850
|
entity |
| Predicate | hasFormerEstate |
P3526
|
FINISHED |
| Object | Warter Priory estate |
—
|
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: Warter Priory estate | Statement: [Warter, East Riding of Yorkshire, hasFormerEstate, Warter Priory estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerEstate Context triple: [Warter, East Riding of Yorkshire, hasFormerEstate, Warter Priory estate]
-
A.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
B.
hadEstates
Indicates that an entity possessed or owned one or more estates (properties or landholdings).
-
C.
occupiesFormerEstateOf
chosen
Indicates that one entity currently resides in, uses, or controls a property that was previously the estate of another entity.
-
D.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
E.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 7:49 p.m.