Triple
T847642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Orleans Mint |
E18311
|
entity |
| Predicate | openedAsMint |
P17359
|
FINISHED |
| Object | 1838 |
—
|
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: 1838 | Statement: [New Orleans Mint, openedAsMint, 1838]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsMint Context triple: [New Orleans Mint, openedAsMint, 1838]
-
A.
closedAsMint
Indicates that an issue, report, or request was resolved and marked as valid or correct in its original form, without requiring changes.
-
B.
openedForCoinage
chosen
Indicates that a facility, system, or process has been made available or activated specifically for the production or issuance of coinage.
-
C.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
openedForSignature
Indicates that an agreement, document, or treaty has been formally made available for eligible parties to sign.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac1e41748190a21cd1ce5ebcb8ff |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.