Triple
T5156178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haddon Hall |
E116313
|
entity |
| Predicate | laterAlterations |
P42870
|
FINISHED |
| Object | Tudor period |
—
|
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: Tudor period | Statement: [Haddon Hall, laterAlterations, Tudor period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAlterations Context triple: [Haddon Hall, laterAlterations, Tudor period]
-
A.
laterModification
chosen
Indicates that one entity is a modification or revision that occurs after another in time.
-
B.
amendedFor
Indicates that one entity has been modified or revised specifically to address, correct, or accommodate another entity.
-
C.
hasAlterationPeriod
Indicates that an entity is associated with a specific time span during which changes, modifications, or alterations may occur or are valid.
-
D.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
E.
decorChanges
Indicates that an entity alters or updates the decorative appearance or arrangement of another entity or environment.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.