Triple
T36481918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Territory Organic Act |
E898837
|
entity |
| Predicate | affectedModernStates |
P23031
|
FINISHED |
| Object | Oregon |
—
|
NE NERFINISHED |
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: Oregon | Statement: [Oregon Territory Organic Act, affectedModernStates, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedModernStates Context triple: [Oregon Territory Organic Act, affectedModernStates, Oregon]
-
A.
modernState
Indicates that an entity functions as a contemporary, currently existing state or nation in the modern era.
-
B.
affectedU.S.State
chosen
Indicates that a particular U.S. state is impacted or influenced by a specified event, condition, or entity.
-
C.
linkedToModernState
Indicates that an entity has a historical, legal, or conceptual connection to a present-day sovereign state.
-
D.
modernStatesInRegion
Indicates that a state is a contemporary/modern political entity located within a specified geographic region.
-
E.
impactOnStates
Indicates the effect or influence that one entity, event, or condition has on the status, condition, or behavior of one or more states.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.