Triple
T5028012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wymondham Priory |
E113223
|
entity |
| Predicate | approximateDissolutionDate |
P34214
|
FINISHED |
| Object | 1538 |
—
|
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: 1538 | Statement: [Wymondham Priory, approximateDissolutionDate, 1538]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDissolutionDate Context triple: [Wymondham Priory, approximateDissolutionDate, 1538]
-
A.
dissolutionTime
chosen
Indicates the point in time at which a relationship, structure, or entity ceases to exist or is formally terminated.
-
B.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
C.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
D.
canBeDissolvedEarly
Indicates that the agreement, contract, or arrangement is allowed to be terminated before its originally specified end date.
-
E.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738d852c8190a122354f1e1f5343 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.