Triple
T31533029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Catherine’s Court |
E804529
|
entity |
| Predicate | underwentAlteration |
P56192
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [St Catherine’s Court, underwentAlteration, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentAlteration Context triple: [St Catherine’s Court, underwentAlteration, 16th century]
-
A.
alterationType
Indicates the specific kind or category of change or modification that has been applied to an entity or relationship.
-
B.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
C.
alteredBy
Indicates that one entity has been changed, modified, or otherwise affected in form, state, or properties as a result of another entity’s action or influence.
-
D.
hasAlterationPeriod
chosen
Indicates that an entity is associated with a specific time span during which changes, modifications, or alterations may occur or are valid.
-
E.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 30, 2026, 10:02 p.m.