Triple
T4346853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grantham House |
E97924
|
entity |
| Predicate | hasAlterationPeriod |
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: [Grantham House, hasAlterationPeriod, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlterationPeriod Context triple: [Grantham House, hasAlterationPeriod, 16th century]
-
A.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
B.
canBeModifiedBetween
Indicates that something is allowed or able to be changed during a specified interval or between defined points or states.
-
C.
hasHistoricalShiftFrom
Indicates a relationship where one state, practice, or condition has been replaced or transformed over time from another earlier state, practice, or condition.
-
D.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
E.
hasDiscoveryPeriod
Indicates the time span during which a particular discovery was made or recognized.
- F. None of above. chosen
Provenance (4 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3518d6728819084a2f40ae0bd3ac8 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b350d1649881908fa6556d875a8b4d |
completed | March 12, 2026, 11:48 p.m. |
Created at: March 12, 2026, 11:15 p.m.