Triple
T32036791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toppenish, Washington |
E818115
|
entity |
| Predicate | muralProgramBeganIn |
P173145
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Toppenish, Washington, muralProgramBeganIn, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: muralProgramBeganIn Context triple: [Toppenish, Washington, muralProgramBeganIn, 1989]
-
A.
muralCompletionYear
Indicates the calendar year in which a mural was completed.
-
B.
muralsPaintedBetween
Indicates that murals were painted during a specific time interval between two given dates or events.
-
C.
muralsNowHeldAt
Indicates that murals, once located elsewhere, are currently kept or displayed at a specified place or institution.
-
D.
hasMuralsFrom
Indicates that a location or structure contains murals that originate from or were created in a specified place or time period.
-
E.
notableMuralCycle
Indicates that an entity is recognized for creating or being associated with a significant, distinguished series of murals.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49bf98c8190b5f3dade19762396 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:18 a.m.