Triple
T13654831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmyra New York Temple |
E326830
|
entity |
| Predicate | openHouseStartDate |
P111000
|
FINISHED |
| Object | March 15, 2000 |
—
|
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: March 15, 2000 | Statement: [Palmyra New York Temple, openHouseStartDate, March 15, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openHouseStartDate Context triple: [Palmyra New York Temple, openHouseStartDate, March 15, 2000]
-
A.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
B.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
-
C.
phase1OpeningDate
Indicates the date on which the first phase of a project, development, or initiative is officially opened or begins operation.
-
D.
exhibitionStartDate
Indicates the date on which an exhibition begins or is first opened to the public.
-
E.
softOpeningDate
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
- F. None of above. chosen
Provenance (4 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60ace048190a4b92310ba272bd1 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:52 p.m.