Triple
T29685500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bank of issue |
E751071
|
entity |
| Predicate | historicallyOftenWas |
P13759
|
FINISHED |
| Object | central bank |
—
|
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: central bank | Statement: [bank of issue, historicallyOftenWas, central bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyOftenWas Context triple: [bank of issue, historicallyOftenWas, central bank]
-
A.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
B.
historicallyIndicates
Indicates that one entity serves as evidence, a sign, or a marker of another entity specifically within a historical context or time period.
-
C.
historicallyConsidered
chosen
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
-
D.
historicallyGivenIn
Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
-
E.
historicallyEncompassed
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 28, 2026, 7:13 p.m.