Triple
T11720190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pullman Historic District |
E278608
|
entity |
| Predicate | designatedNationalMonument |
P89656
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Pullman Historic District, designatedNationalMonument, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedNationalMonument Context triple: [Pullman Historic District, designatedNationalMonument, 2015]
-
A.
designatedNationalMonumentBy
Indicates that an entity has been officially declared a national monument by a specific authority or organization.
-
B.
designatedAsNationalPark
Indicates that an area has been officially assigned the legal status and protections of a national park by an authorized governing body.
-
C.
nationalMonument
Indicates that something has been officially designated as a national monument by a country or governing authority.
-
D.
nationalMonumentDesignationYear
chosen
Indicates the year in which an entity was officially designated as a national monument.
-
E.
yearDesignatedNationalMemorial
Indicates the year in which something was officially designated as a national memorial.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c26e4c8190ae30d906b4fd4221 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.