Triple
T20292115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishops’ Storehouse |
E510052
|
entity |
| Predicate | costToRecipients |
P5902
|
FINISHED |
| Object | typically no cost |
—
|
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: typically no cost | Statement: [Bishops’ Storehouse, costToRecipients, typically no cost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costToRecipients Context triple: [Bishops’ Storehouse, costToRecipients, typically no cost]
-
A.
totalRecipients
Indicates the total number of distinct entities that receive something in the context of the described relationship or action.
-
B.
costToUser
chosen
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
C.
increasedCostFor
Indicates that one entity causes or experiences a rise in the cost associated with another entity or activity.
-
D.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
E.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67700c024819091205f5b0a8648e3 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:12 a.m.