Triple
T16059823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wulfhall, Wiltshire, England |
E389579
|
entity |
| Predicate | partOfEstateOf |
P119206
|
FINISHED |
| Object | Seymour estates in Wiltshire |
—
|
LITERAL FINISHED |
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: Seymour estates in Wiltshire | Statement: [Wulfhall, Wiltshire, England, partOfEstateOf, Seymour estates in Wiltshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfEstateOf Context triple: [Wulfhall, Wiltshire, England, partOfEstateOf, Seymour estates in Wiltshire]
-
A.
partOfEstate
chosen
Indicates that something belongs to, is included within, or forms a component of a particular estate (such as a legal or property estate).
-
B.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
-
C.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
D.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
E.
laterFunctionOfEstate
Indicates that one function or role of an estate occurs at a later time or stage relative to another function of that same 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.