Triple
T5244985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldier King |
E118435
|
entity |
| Predicate | reducedExpenditureOn |
P9925
|
FINISHED |
| Object | court luxury |
—
|
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: court luxury | Statement: [Soldier King, reducedExpenditureOn, court luxury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducedExpenditureOn Context triple: [Soldier King, reducedExpenditureOn, court luxury]
-
A.
reducedCostOf
Indicates that one entity represents a lowered or discounted cost associated with another entity, typically compared to a standard or original price.
-
B.
reduces
chosen
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
C.
reducedDutyRateOn
Indicates a relationship where a reduced customs or tax duty rate is applied to a specified item or transaction.
-
D.
incomeUsedFor
Indicates that some or all of an income amount is allocated or spent for a specified purpose, activity, or recipient.
-
E.
reducedPowerOf
Indicates that one entity has a diminished or weakened level of power, authority, or effectiveness relative to another or to its previous state.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4fa0ec8190bce3da09aa768726 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.