Triple
T28452112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Infrastructure Levy |
E716604
|
entity |
| Predicate | rateSetBy |
P137944
|
FINISHED |
| Object | charging schedule |
—
|
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: charging schedule | Statement: [Community Infrastructure Levy, rateSetBy, charging schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rateSetBy Context triple: [Community Infrastructure Levy, rateSetBy, charging schedule]
-
A.
rate
Indicates the numerical evaluation or assessment assigned by one entity to another based on perceived quality, performance, or value.
-
B.
setsPolicyRate
Indicates that an entity determines and establishes the official policy interest rate applied within a monetary or regulatory framework.
-
C.
usesRatesSetBy
chosen
Indicates that one entity applies or follows the pricing or rate structure determined by another entity.
-
D.
rechargeRate
Indicates the rate or speed at which something restores or replenishes its capacity, energy, or resources over time.
-
E.
rateDefinition
Indicates that one entity specifies or defines the rate or ratio at which another entity changes, is applied, or is measured.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e72b5208190869d49fcb3f0a546 |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:52 a.m.