Triple
T26437457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hull Mint House, Boston |
E664989
|
entity |
| Predicate | endTimeAsMint |
P109877
|
FINISHED |
| Object | late 17th century |
—
|
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: late 17th century | Statement: [Hull Mint House, Boston, endTimeAsMint, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeAsMint Context triple: [Hull Mint House, Boston, endTimeAsMint, late 17th century]
-
A.
mintedUntil
chosen
Indicates the time or condition up to which something can be or was produced, issued, or created (e.g., coins, tokens, or similar items).
-
B.
endTimeAsMP
Indicates the time at which an event or state concludes, expressed in minutes past midnight.
-
C.
mintedAt
Indicates the specific time or block at which a digital asset or token was created (minted) on a blockchain.
-
D.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
E.
endAt
Indicates that an event, process, or state concludes or terminates at a specified time, location, or condition.
- 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_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 11:55 p.m.