Triple
T30750959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostankino Palace |
E782954
|
entity |
| Predicate | openingDateAsEstate |
P85309
|
FINISHED |
| Object | late 18th century |
—
|
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: late 18th century | Statement: [Ostankino Palace, openingDateAsEstate, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateAsEstate Context triple: [Ostankino Palace, openingDateAsEstate, late 18th century]
-
A.
openingDateApproximate
chosen
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
B.
openHouseStartDate
Indicates the calendar date on which an open house event for a property is scheduled to begin.
-
C.
openingDateAsCondorFlats
Indicates the date on which something was opened specifically under the designation or theme of "Condor Flats."
-
D.
openingDateAsThroughLine
Indicates that the opening date is used as a continuous reference or organizing thread linking related events, records, or states over time.
-
E.
openingDateLine15
Indicates the date on which line 15 (e.g., a specific route, service, or infrastructure segment) was officially opened or began operation.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:39 p.m.