Triple
T2700348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stowe House |
E59213
|
entity |
| Predicate | financialProblemsLedTo |
P24789
|
FINISHED |
| Object | sale of contents in 1848 |
—
|
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: sale of contents in 1848 | Statement: [Stowe House, financialProblemsLedTo, sale of contents in 1848]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialProblemsLedTo Context triple: [Stowe House, financialProblemsLedTo, sale of contents in 1848]
-
A.
hasEconomicChallenge
chosen
Indicates that an entity is experiencing or facing a financial or economic difficulty, constraint, or problem.
-
B.
problems
Indicates that one entity has issues, difficulties, or complications associated with or caused by another entity.
-
C.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
D.
fiscalIssue
Indicates a relationship where an entity is involved in, affected by, or associated with a financial or budgetary problem, concern, or matter.
-
E.
economicSectorIssue
Indicates that there is a problem, challenge, or concern affecting a particular economic sector.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda34ba508190be8e2c9e4052adfc |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.