Triple
T6520052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNB |
E148356
|
entity |
| Predicate | cannotIssue |
P16359
|
FINISHED |
| Object | Swiss franc coins |
—
|
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: Swiss franc coins | Statement: [SNB, cannotIssue, Swiss franc coins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotIssue Context triple: [SNB, cannotIssue, Swiss franc coins]
-
A.
doesNotIssue
chosen
Indicates that one entity refrains from or fails to produce, grant, or distribute something (such as a document, order, or resource) to another entity.
-
B.
cannotGrant
Indicates that an entity lacks the authority, permission, or ability to confer a requested right, access, or resource to another entity.
-
C.
cannotReview
Indicates that an entity is not permitted or able to perform a review of another entity or item.
-
D.
cannotIntroduce
Indicates that one entity is not permitted or able to introduce another entity (such as a person, concept, or item) into a given context or to a third party.
-
E.
cannotOffer
Indicates that one entity is unable or not permitted to provide, propose, or extend an offer to another entity.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad92c624819086dbb12b4f6b78d3 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.