Triple
T9989640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Territory |
E196851
|
entity |
| Predicate | organizedStatus |
P91449
|
FINISHED |
| Object | organized territory |
—
|
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: organized territory | Statement: [Iowa Territory, organizedStatus, organized territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedStatus Context triple: [Iowa Territory, organizedStatus, organized territory]
-
A.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
B.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
C.
organizedDuring
Indicates that an event or activity was arranged or took place within a specified time period or temporal context.
-
D.
organizationalStatus
Indicates the current state or condition of an organization within a defined context, such as its operational, legal, or membership status.
-
E.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
- F. None of above. chosen
Provenance (4 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdc79f3df08190ab3094ad1cd5490f |
completed | April 2, 2026, 1:34 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:50 p.m.