Triple
T30546721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vandalia State House State Historic Site |
E777438
|
entity |
| Predicate | startOfUseAsStateCapitol |
P85520
|
FINISHED |
| Object | 1836 |
—
|
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: 1836 | Statement: [Vandalia State House State Historic Site, startOfUseAsStateCapitol, 1836]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfUseAsStateCapitol Context triple: [Vandalia State House State Historic Site, startOfUseAsStateCapitol, 1836]
-
A.
periodAsDeFactoCapitalStart
chosen
Indicates the point in time when a location begins functioning as the de facto capital, even if not officially designated as such.
-
B.
inauguratedAsCapital
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
C.
usedAsCapitolUntil
Indicates that a place served as the official capital of a political entity up to a specified end time.
-
D.
announcedAsNewCapitalOn
Indicates that a location was officially declared or designated as a new capital on a specific date.
-
E.
servedAsStateCapitalUntil
Indicates that a location functioned as the official capital of a state up to a specified end 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: April 29, 2026, 8:19 p.m.