Triple
T30522376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safeway Inc. (historical headquarters) |
E776731
|
entity |
| Predicate | startTimeAsHeadquarters |
P60856
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Safeway Inc. (historical headquarters), startTimeAsHeadquarters, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsHeadquarters Context triple: [Safeway Inc. (historical headquarters), startTimeAsHeadquarters, 1996]
-
A.
headquartersLocationTime
Indicates the location where an entity’s headquarters is situated during a specified time period.
-
B.
endTimeAsHeadquarters
Indicates the time at which an entity’s role or status as a headquarters comes to an end.
-
C.
timePeriodAsMainHeadquartersStart
chosen
Indicates the point in time when a location first became the main headquarters for an entity.
-
D.
startTimeAsSuperiorGeneral
Indicates the point in time when an individual begins serving in the role of Superior General.
-
E.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: April 29, 2026, 8:17 p.m.