Triple
T4211220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyringham Hall |
E93904
|
entity |
| Predicate | hasLaterAlterationsPeriod |
P42870
|
FINISHED |
| Object | early 20th 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: early 20th century | Statement: [Tyringham Hall, hasLaterAlterationsPeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterAlterationsPeriod Context triple: [Tyringham Hall, hasLaterAlterationsPeriod, early 20th century]
-
A.
laterModification
chosen
Indicates that one entity is a modification or revision that occurs after another in time.
-
B.
hasHistoricalShiftFrom
Indicates a relationship where one state, practice, or condition has been replaced or transformed over time from another earlier state, practice, or condition.
-
C.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
D.
hasHistoricalShiftTo
Indicates a change over time in which one state, condition, or configuration is replaced or transformed into another in a historically traceable way.
-
E.
amendedAt
Indicates the date and time at which an existing entity or record was modified or updated.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.