Triple
T30507303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atascadero City Hall |
E776307
|
entity |
| Predicate | restorationCompletedYear |
P9623
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Atascadero City Hall, restorationCompletedYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationCompletedYear Context triple: [Atascadero City Hall, restorationCompletedYear, 2013]
-
A.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
B.
restorationPremieredAt
Indicates that a particular restoration of a work had its first public showing or debut at a specific event, venue, or location.
-
C.
reconstructionYear
chosen
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
D.
rebuiltApproximateEndYear
Indicates that an entity was rebuilt, with the specified year representing an approximate (not exact) end date of the rebuilding process.
-
E.
reconstructionEndDate
Indicates the date on which a reconstruction process or project is completed.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687b4dddc8190a59fd13d2f8a2e16 |
completed | May 2, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:15 p.m.