Triple
T17140345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creditor Reporting System statistics |
E415944
|
entity |
| Predicate | dataGranularity |
P109501
|
FINISHED |
| Object | activity-level |
—
|
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: activity-level | Statement: [Creditor Reporting System statistics, dataGranularity, activity-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataGranularity Context triple: [Creditor Reporting System statistics, dataGranularity, activity-level]
-
A.
timeGranularity
Indicates the level of temporal detail or precision at which an event, measurement, or relationship is defined (e.g., seconds, days, months).
-
B.
granularityLevel
chosen
Indicates the degree of detail or resolution at which something is specified, measured, or analyzed within a given context.
-
C.
timeTravelGranularity
Indicates the level of temporal precision or resolution at which time travel or time-based operations can occur between entities.
-
D.
pricingGranularity
Indicates the level of detail or resolution at which prices are defined, grouped, or applied within a pricing structure or model.
-
E.
controlGranularity
Indicates the level of detail or fineness with which control or regulation is applied within a given process or system.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d44a508190a3a149c3a64957f5 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.