Triple
T29685511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bank of issue |
E751071
|
entity |
| Predicate | mayHaveMonopolyOn |
P2908
|
FINISHED |
| Object | note issuance |
—
|
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: note issuance | Statement: [bank of issue, mayHaveMonopolyOn, note issuance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveMonopolyOn Context triple: [bank of issue, mayHaveMonopolyOn, note issuance]
-
A.
isMonopoly
Indicates that one entity exclusively controls a market or resource, facing no significant competition.
-
B.
monopolyOn
chosen
Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
-
C.
monopolyGrantedBy
Indicates that one party has been given exclusive control or rights over a market, resource, or activity by another authority or entity.
-
D.
monopolyRestricted
Indicates that an entity’s monopoly power or exclusive control over a market, resource, or service is limited, regulated, or otherwise constrained.
-
E.
monopolySetWith
Indicates that the related entities together form a monopoly, such that they exclusively control a market or resource without effective competition.
- 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_69f67290186481908e59be35101a1817 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:13 p.m.