Triple
T26580662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1892–1893 Columbian Exposition half dollar |
E667067
|
entity |
| Predicate | reverseDateInscription |
P160661
|
FINISHED |
| Object | 1892 |
—
|
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: 1892 | Statement: [1892–1893 Columbian Exposition half dollar, reverseDateInscription, 1892]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseDateInscription Context triple: [1892–1893 Columbian Exposition half dollar, reverseDateInscription, 1892]
-
A.
reverseInscription
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
-
B.
icoDate
Indicates the date on which an initial coin offering (ICO) occurs or is scheduled to occur.
-
C.
reverseInscriptionMeaning
Indicates that the inscription’s meaning is the reverse or opposite of the usual or expected interpretation.
-
D.
reformDate
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
E.
deciphermentDate
Indicates the date on which something (such as a text, code, or inscription) was successfully deciphered or decoded.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614e0f3688190a10114486c5d62ab |
completed | May 2, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 2:03 a.m.