Triple
T33481512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Osnabrück |
E857484
|
entity |
| Predicate | couldMint |
P129201
|
FINISHED |
| Object | coins (in some periods) |
—
|
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: coins (in some periods) | Statement: [Prince-Bishop of Osnabrück, couldMint, coins (in some periods)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldMint Context triple: [Prince-Bishop of Osnabrück, couldMint, coins (in some periods)]
-
A.
typeOfMint
Indicates that one entity is a specific kind or variety of mint relative to another entity.
-
B.
hadCentralMint
chosen
Indicates that an entity possessed or operated a primary facility responsible for minting currency.
-
C.
hasMintmaster
Indicates that an entity has, is associated with, or is overseen by a specific mintmaster responsible for minting or issuing it.
-
D.
mint
Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
-
E.
closedAsMint
Indicates that an issue, report, or request was resolved and marked as valid or correct in its original form, without requiring changes.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52fd4bc8190a18d0cd7dad5c6bf |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.