Triple
T450397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anchorage |
E7113
|
entity |
| Predicate | consolidatedAsMunicipality |
P12293
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Anchorage, consolidatedAsMunicipality, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consolidatedAsMunicipality Context triple: [Anchorage, consolidatedAsMunicipality, 1975]
-
A.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
B.
incorporatedAsTownIn
Indicates that an entity was officially established and given legal status as a town within a specified jurisdiction.
-
C.
incorporatedAsTownship
Indicates that an area or community has been formally established and recognized as a township through a legal or governmental incorporation process.
-
D.
incorporatedAsCity
Indicates that an entity was formally established and legally recognized as a city.
-
E.
consolidatedAs
chosen
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef691cc8819091729eaac52c9457 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.