Triple
T27330124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasigluk, Alaska |
E689773
|
entity |
| Predicate | federalCodeType |
P58137
|
FINISHED |
| Object | FIPS code |
—
|
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: FIPS code | Statement: [Kasigluk, Alaska, federalCodeType, FIPS code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalCodeType Context triple: [Kasigluk, Alaska, federalCodeType, FIPS code]
-
A.
federalGovernmentCode
chosen
Indicates that an entity is associated with, identified by, or governed under a specific code or classification defined by the federal government.
-
B.
labelCodeType
Indicates that one entity serves as the type or classification scheme for the labeling code applied to another entity.
-
C.
federalStateCode
Indicates that an entity is associated with, governed by, or identified through a specific federal state code within a country’s administrative or legal system.
-
D.
federalStatus
Indicates that an entity holds a particular legal or administrative status under federal (national) authority or jurisdiction.
-
E.
filingTypeCode
Indicates the specific category or type of filing associated with a submitted document or record.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:37 a.m.