Triple
T7431292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computer History Museum |
E171493
|
entity |
| Predicate | buildingOpenedToPublic |
P18212
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Computer History Museum, buildingOpenedToPublic, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingOpenedToPublic Context triple: [Computer History Museum, buildingOpenedToPublic, 2002]
-
A.
openedToPublicAsMuseum
Indicates that a place or building was made accessible to the general public specifically in the capacity of a museum.
-
B.
openedToPublicBy
Indicates that an entity was made accessible or available to the general public through the action or decision of another entity.
-
C.
openedForPublic
chosen
Indicates that something has been made accessible or available for use, entry, or participation by the general public.
-
D.
openedToPublicAsZoo
Indicates that a place or facility was officially made accessible to the general public specifically as a zoo.
-
E.
openedToPublicAsMonument
Indicates that something was officially made accessible to the general public in the capacity or status of a monument.
- 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.