Triple
T31306337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee |
E798343
|
entity |
| Predicate | hasStateCapitalBuilding |
P14010
|
FINISHED |
| Object | Tennessee State Capitol |
—
|
NE NERFINISHED |
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: Tennessee State Capitol | Statement: [Tennessee, hasStateCapitalBuilding, Tennessee State Capitol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateCapitalBuilding Context triple: [Tennessee, hasStateCapitalBuilding, Tennessee State Capitol]
-
A.
stateCapitalBuilding
chosen
Indicates that a building serves as the primary governmental capitol facility for a specific state.
-
B.
isStateCapital
Indicates that a city serves as the official capital of a given state.
-
C.
stateCapitalBuildingLocation
Indicates the spatial location of a state’s capital building relative to a specified place or area.
-
D.
hasFederalCapitalWithin
Indicates that a country or federal entity has its official federal capital city located within the boundaries of a specified geographic area.
-
E.
isLegislativeCapitalOf
Indicates that a location serves as the primary seat of a region’s legislative branch or lawmaking body.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: April 29, 2026, 9:14 p.m.