Triple
T1027337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Alaska |
E22168
|
entity |
| Predicate | hasCapitalUntil |
P13207
|
FINISHED |
| Object | Sitka, 1906 |
—
|
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: Sitka, 1906 | Statement: [District of Alaska, hasCapitalUntil, Sitka, 1906]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalUntil Context triple: [District of Alaska, hasCapitalUntil, Sitka, 1906]
-
A.
hasCapital
Indicates that a place or political entity has a specific city designated as its capital.
-
B.
hasCapitalType
Indicates that a specified location’s capital is of a particular type (e.g., political, administrative, or economic capital).
-
C.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
D.
basedInUntil
Indicates that an entity was based or located in a particular place up to a specified end time or date, after which this association ceased.
-
E.
servedAsNationalCapitalUntil
chosen
Indicates that a place functioned as the national capital of a country or state up to a specified end date, after which it no longer held that status.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7276180819085c6b23501a6a6e0 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.