Triple
T21613196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faversham Abbey |
E533360
|
entity |
| Predicate | hasSiteUseAfterDissolution |
P40416
|
FINISHED |
| Object | private estate |
—
|
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: private estate | Statement: [Faversham Abbey, hasSiteUseAfterDissolution, private estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteUseAfterDissolution Context triple: [Faversham Abbey, hasSiteUseAfterDissolution, private estate]
-
A.
siteUseAfterDemolition
Indicates the subsequent use or function assigned to a site following the demolition of its previous structures.
-
B.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
C.
hasDissolutionDate
Indicates the date on which an entity, such as an organization or legal arrangement, formally ceases to exist or is officially dissolved.
-
D.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
E.
functionAfterDissolution
chosen
Indicates that one function, role, or operation occurs or continues after the dissolution or termination of another entity or structure.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3ba8d7cc8190a59706896a4c073a |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.