Triple
T164103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRB |
E2972
|
entity |
| Predicate | typeOfIndependence |
P5525
|
FINISHED |
| Object | Operational independence in monetary policy |
—
|
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: Operational independence in monetary policy | Statement: [FRB, typeOfIndependence, Operational independence in monetary policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfIndependence Context triple: [FRB, typeOfIndependence, Operational independence in monetary policy]
-
A.
independenceFrom
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
B.
resultOfIndependence
Indicates that something exists or occurs as a consequence or outcome of an independence event or process.
-
C.
independenceRecognized
Indicates that one entity formally acknowledges another entity’s status as independent and self-governing.
-
D.
independenceDeclaredBy
Indicates that an entity’s independence was formally proclaimed or established by another specified entity.
-
E.
independenceYear
Indicates the year in which an entity achieved political independence or was formally recognized as independent.
- F. None of above. chosen
Provenance (4 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258827da481909b20ea5e9d21676f |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2566392208190a538ea9aa1fac53e |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257101060819094db0f3a3a72f312 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.