Triple
T7431293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computer History Museum |
E171493
|
entity |
| Predicate | grandReopening |
P10067
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Computer History Museum, grandReopening, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandReopening Context triple: [Computer History Museum, grandReopening, 2011]
-
A.
reopeningAs
Indicates that an entity that was previously closed or inactive is starting operations again under a new or updated form, identity, or function.
-
B.
reopeningDate
chosen
Indicates the date on which something that was previously closed is opened again for use or access.
-
C.
reopeningPerformance
Indicates the performance or outcome associated with resuming or restarting an activity, operation, or service after it has been closed or suspended.
-
D.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
E.
fullyReopened
Indicates that something previously closed or partially open has been restored to complete, unrestricted operational status.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f324afac8190b34fcac95fd57410 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.