Triple
T26437352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coining the "Pine Tree Shilling" |
E664986
|
entity |
| Predicate | currencyFor |
P245
|
FINISHED |
| Object | New England |
—
|
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: New England | Statement: [Coining the "Pine Tree Shilling", currencyFor, New England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyFor Context triple: [Coining the "Pine Tree Shilling", currencyFor, New England]
-
A.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to another entity.
-
B.
currencyUsedFor
Indicates that a particular currency is used as the medium of exchange or legal tender for a given entity, such as a country, region, or organization.
-
C.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
D.
currency
chosen
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
E.
currencyForm
Indicates that one entity is a specific monetary form, denomination, or variant of the currency represented by the other 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 26, 2026, 11:55 p.m.