Triple
T8744611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukuntuweap National Monument |
E207792
|
entity |
| Predicate | redesignatedOn |
P73142
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [Mukuntuweap National Monument, redesignatedOn, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redesignatedOn Context triple: [Mukuntuweap National Monument, redesignatedOn, 1919]
-
A.
redesignationYear
chosen
Indicates the year in which something was officially redesignated, renamed, or assigned a new status or classification.
-
B.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
C.
rededicationDate
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
D.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
-
E.
reaffirmedOn
Indicates that a prior decision, statement, or agreement was confirmed or validated again on a specific date or occasion.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d72e47c819099540d062d35ebd5 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:38 p.m.