Triple
T5224099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strawberry Hill sale of 1842 |
E117941
|
entity |
| Predicate | reasonForSale |
P62132
|
FINISHED |
| Object | dispersal of Horace Walpole’s collection |
—
|
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: dispersal of Horace Walpole’s collection | Statement: [Strawberry Hill sale of 1842, reasonForSale, dispersal of Horace Walpole’s collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForSale Context triple: [Strawberry Hill sale of 1842, reasonForSale, dispersal of Horace Walpole’s collection]
-
A.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
-
B.
reasonForDelisting
Indicates the specific cause or justification for which an item, entity, or record has been removed from a list or registry.
-
C.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
D.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
E.
abandonedReason
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7abd3ed48190bfd8d2f2ca399741 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78a89b608190b259d3d8658f8f7c |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:48 p.m.