Triple
T18197663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIS international banking statistics |
E435702
|
entity |
| Predicate | timeSeries |
P38785
|
FINISHED |
| Object | quarterly data |
—
|
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: quarterly data | Statement: [BIS international banking statistics, timeSeries, quarterly data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSeries Context triple: [BIS international banking statistics, timeSeries, quarterly data]
-
A.
timeInSeries
Indicates that one temporal value occurs within the duration or sequence span defined by another in a series.
-
B.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
C.
timeSampling
chosen
Indicates that one entity specifies how or at what intervals another entity is sampled or measured over time.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodAnalyzed
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d47f1c819082eec59492497797 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.