Triple
T35319029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolesław III the Generous |
E1019984
|
entity |
| Predicate | spendingStyle |
P182729
|
FINISHED |
| Object | extravagant |
—
|
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: extravagant | Statement: [Bolesław III the Generous, spendingStyle, extravagant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spendingStyle Context triple: [Bolesław III the Generous, spendingStyle, extravagant]
-
A.
typeOfSpendingAffected
Indicates that a particular kind or category of spending is influenced, changed, or impacted by another factor or event.
-
B.
positionOnSpending
Indicates a stance or viewpoint an entity holds regarding levels or patterns of spending, such as how much should be spent and on what.
-
C.
spendSize
Indicates the amount or magnitude of spending associated with an entity or transaction.
-
D.
spendingRequires
Indicates that performing a spending action is contingent upon satisfying a specified requirement or condition.
-
E.
overseesSpendingOf
Indicates that one entity has authority to monitor, direct, or control how another entity’s funds or budget are used.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79096a88081908cb64c02c31c72a0 |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.