Triple
T35655332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandsfoot Castle |
E1030266
|
entity |
| Predicate | fellIntoDisuse |
P172267
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Sandsfoot Castle, fellIntoDisuse, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fellIntoDisuse Context triple: [Sandsfoot Castle, fellIntoDisuse, 17th century]
-
A.
fellIntoNeglect
Indicates that something previously maintained or attended to was no longer cared for and gradually deteriorated or was forgotten.
-
B.
ceasedToBeUsed
chosen
Indicates that something that was previously in use has stopped being used from a certain point in time onward.
-
C.
defunct
Indicates that an entity has ceased to exist, operate, or function and is no longer active or in use.
-
D.
eraOfObsolescence
Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
-
E.
mothballedIn
Indicates that something has been taken out of active use and placed into storage or reserve at a particular time or under specific conditions.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7760dc819093f81b4e6d4db793 |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.