Triple
T32922735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri Executive Order 44 |
E842187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical government document |
C27413
|
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: historical government document Context triple: [Missouri Executive Order 44, instanceOf, historical government document]
-
A.
historical political document
chosen
A historical political document is an official or influential written record produced in a past political context that reflects, shapes, or codifies governmental decisions, ideologies, or power relations of its time.
-
B.
government document collection
A government document collection is an organized set of official records, reports, laws, and publications produced or issued by governmental bodies, maintained for reference, accountability, and public access.
-
C.
founding document
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
D.
historical scientific document
A historical scientific document is an original written or printed record from the past that presents, analyzes, or communicates scientific observations, theories, experiments, or methods within its contemporary context.
-
E.
government-sponsored documentation project
A government-sponsored documentation project is an officially funded and managed initiative to systematically collect, record, and preserve information, data, or cultural materials for public, administrative, or historical purposes.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.