Triple
T17232917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Blue Book |
E418288
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | official state fact book |
C1956
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: official state fact book Context triple: [Oregon Blue Book, instanceOf, official state fact book]
-
A.
official state list
An official state list is an authoritative, government-sanctioned enumeration of entities (such as states, regions, or recognized bodies) that defines their legal or administrative status within a jurisdiction.
-
B.
official statistics release
An official statistics release is an authoritative publication by a recognized body that presents validated, methodologically sound quantitative data and analysis on specific topics for public, policy, and research use.
-
C.
federal government database
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
-
D.
federal government database
A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
-
E.
official publication
chosen
An official publication is an authoritative document or work formally issued by a recognized organization or government body to communicate sanctioned information, policies, or records.
- F. None of above.
Provenance (1 batch)
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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:39 a.m.