Triple
T26176148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petersville |
E654546
|
entity |
| Predicate | isLocatedInBoroughSeatRegion |
P43690
|
FINISHED |
| Object | Wasilla area |
—
|
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: Wasilla area | Statement: [Petersville, isLocatedInBoroughSeatRegion, Wasilla area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInBoroughSeatRegion Context triple: [Petersville, isLocatedInBoroughSeatRegion, Wasilla area]
-
A.
isBoroughSeatOf
Indicates that a place serves as the administrative center or seat of government for a specific borough.
-
B.
isCentralBoroughOf
Indicates that a borough serves as the primary or central administrative or geographic district of a specified city or region.
-
C.
locatedInBoroughCommunityDistrict
chosen
Indicates that something is situated within a specific borough community district.
-
D.
locatedInFormerBorough
Indicates that an entity is or was situated within the geographic area of a borough that no longer exists as an administrative unit.
-
E.
wasBoroughOf
Indicates that one place previously held the administrative or territorial status of a borough within another jurisdiction.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 8:37 p.m.