Triple
T34416386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holt Castle |
E883411
|
entity |
| Predicate | lostFeature |
P163725
|
FINISHED |
| Object | most of its above-ground masonry |
—
|
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: most of its above-ground masonry | Statement: [Holt Castle, lostFeature, most of its above-ground masonry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostFeature Context triple: [Holt Castle, lostFeature, most of its above-ground masonry]
-
A.
lostFunction
Indicates that an entity no longer possesses or can perform a function or capability it previously had.
-
B.
lostSupportOf
Indicates that one entity no longer has the backing, approval, or endorsement of another entity that previously supported it.
-
C.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
-
D.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
E.
lostPart
chosen
Indicates that an entity has become separated from and no longer possesses a specific part that once belonged to it.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.