Triple
T10186711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Fort Wayne (1809) |
E236928
|
entity |
| Predicate | cessionArea |
P1586
|
FINISHED |
| Object | approximately 3,000,000 acres of Native American land |
—
|
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: approximately 3,000,000 acres of Native American land | Statement: [Treaty of Fort Wayne (1809), cessionArea, approximately 3,000,000 acres of Native American land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cessionArea Context triple: [Treaty of Fort Wayne (1809), cessionArea, approximately 3,000,000 acres of Native American land]
-
A.
regionOfLoss
Indicates the anatomical or spatial area where a loss, damage, or deficit occurs or is localized.
-
B.
affectedArea
chosen
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
C.
disasterLocation
Indicates the place where a disaster occurs or has its primary impact.
-
D.
areaDestroyed
Indicates that a specified portion or region has been damaged or ruined to the point of destruction.
-
E.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded790b488190b1ed4645554873cd |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.