Triple
T85818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knoxville, Tennessee |
E1727
|
entity |
| Predicate | servedAsStateCapitalUntil |
P4316
|
FINISHED |
| Object | 1812 |
—
|
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: 1812 | Statement: [Knoxville, Tennessee, servedAsStateCapitalUntil, 1812]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsStateCapitalUntil Context triple: [Knoxville, Tennessee, servedAsStateCapitalUntil, 1812]
-
A.
servedAsUSCapitalUntil
Indicates that a place functioned as the capital of the United States up to a specified end date.
-
B.
servedAsUSCapitalFrom
Indicates that a location functioned as the capital of the United States during a specified time period.
-
C.
stateCapitalSince
Indicates that one location has served as the official capital of a state continuously from a specified starting time.
-
D.
capitalOfProvincePreviouslyLocatedOn
Indicates that an entity serves or served as the capital city of a province that was formerly situated in a specified location.
-
E.
relocatedToWashingtonYear
Indicates the year in which an entity moved or was transferred to Washington as its new location.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24eb59e808190811c20518f39b1cc |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a250e2a80881909e5a653260e6f8e0 |
completed | Feb. 28, 2026, 2:20 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.