Triple
T412687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery, Alabama |
E9524
|
entity |
| Predicate | becameStateCapitalIn |
P5604
|
FINISHED |
| Object | 1846 |
—
|
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: 1846 | Statement: [Montgomery, Alabama, becameStateCapitalIn, 1846]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameStateCapitalIn Context triple: [Montgomery, Alabama, becameStateCapitalIn, 1846]
-
A.
servedAsStateCapitalFrom
Indicates that one place functioned as the official state capital of a political entity during a specified time period.
-
B.
servedAsStateCapitalUntil
Indicates that a location functioned as the official capital of a state up to a specified end date.
-
C.
inauguratedAsCapital
chosen
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
D.
wasStateCapitalOf
Indicates that a city previously served as the official capital of a specified state or equivalent political region.
-
E.
stateCapitalSince
Indicates that one location has served as the official capital of a state continuously from a specified starting time.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdc422881908910428fd1aee7c6 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.