Triple
T30427014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station (Seattle) |
E774059
|
entity |
| Predicate | reopenedAsOffices |
P169415
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Union Station (Seattle), reopenedAsOffices, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsOffices Context triple: [Union Station (Seattle), reopenedAsOffices, 1999]
-
A.
reorganizedOfficeOf
Indicates that one entity has restructured, reshaped, or otherwise reorganized the organizational structure or functions of another entity’s office.
-
B.
replacedOffice
Indicates that one office or position has been succeeded or taken over by another, replacing it in its former role or function.
-
C.
reopenedAsAssayOffice
Indicates that an entity, previously closed or repurposed, was later reopened specifically to function as an assay office.
-
D.
reopenedInNewBuilding
Indicates that an entity, after being closed or relocated, has resumed operations in a different, newly constructed building.
-
E.
officeReconstitutedIn
Indicates that an official position or office was re-established or newly formed within a specified location or jurisdiction.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6866990548190aea96f3a46ba2e43 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:06 p.m.