Triple
T26071946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susitna North |
E657572
|
entity |
| Predicate | previousCensusAreaName |
P75936
|
FINISHED |
| Object | Y Community |
—
|
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: Y Community | Statement: [Susitna North, previousCensusAreaName, Y Community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCensusAreaName Context triple: [Susitna North, previousCensusAreaName, Y Community]
-
A.
previousCensus
Indicates that one census event temporally precedes another in an ordered sequence of censuses.
-
B.
formerNameOfAreaWithin
chosen
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
-
C.
previousProvince
Indicates that one province was the immediately preceding administrative region of another in a temporal or historical sequence.
-
D.
censusAreaPreBorough
Indicates that a specified area measurement corresponds to the census-defined area of a place before it was organized into boroughs.
-
E.
previousCounty
Indicates that one county was the immediately preceding county associated with an entity before the current or later county.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 26, 2026, 7:30 p.m.