Triple
T3213021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steakhouse 71 |
E67324
|
entity |
| Predicate | openingYearReference |
P2467
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Steakhouse 71, openingYearReference, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingYearReference Context triple: [Steakhouse 71, openingYearReference, 1971]
-
A.
officialOpeningYear
chosen
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
B.
originYear
Indicates the year in which something first originated, was created, or began.
-
C.
openingEra
Indicates the historical period or era during which something (such as a structure, institution, or work) was first opened or began operation.
-
D.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
E.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaabba8e481909118d9f888ddcd63 |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.