Triple
T26437349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coining the "Pine Tree Shilling" |
E664986
|
entity |
| Predicate | hasMintmaster |
P168920
|
FINISHED |
| Object | John Hull |
—
|
NE NERFINISHED |
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: John Hull | Statement: [Coining the "Pine Tree Shilling", hasMintmaster, John Hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMintmaster Context triple: [Coining the "Pine Tree Shilling", hasMintmaster, John Hull]
-
A.
hadCentralMint
Indicates that an entity possessed or operated a primary facility responsible for minting currency.
-
B.
typeOfMint
Indicates that one entity is a specific kind or variety of mint relative to another entity.
-
C.
hasMasters
Indicates that an entity possesses or has obtained one or more master’s-level degrees.
-
D.
hasMast
Indicates that an object possesses or is equipped with a mast as part of its structure.
-
E.
operatedMintIn
Indicates that an entity operated or managed a minting facility or operation within a specified location or jurisdiction.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 26, 2026, 11:55 p.m.