Triple
T2446656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri Compromise |
E53609
|
entity |
| Predicate | freeStatesCountChange |
P33927
|
FINISHED |
| Object | increased by admitting Maine |
—
|
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: increased by admitting Maine | Statement: [Missouri Compromise, freeStatesCountChange, increased by admitting Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freeStatesCountChange Context triple: [Missouri Compromise, freeStatesCountChange, increased by admitting Maine]
-
A.
numberOfStates
Indicates the total count of distinct states or conditions associated with an entity or system.
-
B.
deltaState
chosen
Indicates a change or transition in the state or condition of an entity between two points in time.
-
C.
hasNumberOfCounties
Indicates the relationship that specifies how many counties are associated with or contained within a given entity.
-
D.
affectedU.S.State
Indicates that a particular U.S. state is impacted or influenced by a specified event, condition, or entity.
-
E.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.