Triple
T278917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Estate |
E5310
|
entity |
| Predicate | revenueUsedFor |
P2874
|
FINISHED |
| Object | benefit of the public finances |
—
|
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: benefit of the public finances | Statement: [Crown Estate, revenueUsedFor, benefit of the public finances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revenueUsedFor Context triple: [Crown Estate, revenueUsedFor, benefit of the public finances]
-
A.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
B.
revenueLevel
Indicates the relative amount or tier of revenue associated with an entity or activity.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedInTaxPayments
chosen
Indicates that something is employed or applied as part of making or fulfilling tax payments.
-
E.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25def95c48190bb8ab2259f67b583 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.