Triple
T21217504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Monument |
E522873
|
entity |
| Predicate | dateOpenedToPublic |
P84798
|
FINISHED |
| Object | 1888 |
—
|
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: 1888 | Statement: [Washington Monument, dateOpenedToPublic, 1888]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOpenedToPublic Context triple: [Washington Monument, dateOpenedToPublic, 1888]
-
A.
openedToPublicBy
Indicates that an entity was made accessible or available to the general public through the action or decision of another entity.
-
B.
yearOpenedToPublic
chosen
Indicates the calendar year in which something (such as a place, facility, or service) was first made accessible to the general public.
-
C.
openToPublicSince
Indicates that an entity has been accessible or available for use by the general public starting from a specified point in time.
-
D.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
E.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734744dcc81908b3065adc93b4b98 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:41 p.m.