Triple
T2004718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Cases Review Commission |
E43553
|
entity |
| Predicate | applicationFee |
P25908
|
FINISHED |
| Object | no fee |
—
|
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: no fee | Statement: [Criminal Cases Review Commission, applicationFee, no fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationFee Context triple: [Criminal Cases Review Commission, applicationFee, no fee]
-
A.
feePolicy
chosen
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
B.
featuresCharge
Indicates that one entity includes, offers, or is characterized by a particular charge (such as a fee, cost, or pricing component).
-
C.
admissionFee
Indicates the monetary charge required for entry or participation in a place, event, or activity.
-
D.
fareIntegration
Indicates that multiple transportation services or modes share a coordinated fare system, allowing passengers to use a single payment or ticket across them.
-
E.
centralCharge
Indicates that an entity has a specific central charge value, typically quantifying a key parameter in a conformal or related physical or mathematical theory.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb89717c88190ba506134c671d386 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.