Triple
T13154464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of La Pointe |
E312546
|
entity |
| Predicate | cededLandArea |
P108811
|
FINISHED |
| Object | large areas around Lake Superior |
—
|
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: large areas around Lake Superior | Statement: [Treaty of La Pointe, cededLandArea, large areas around Lake Superior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cededLandArea Context triple: [Treaty of La Pointe, cededLandArea, large areas around Lake Superior]
-
A.
cededLandFor
Indicates that one party transferred control or ownership of land to another party, typically as part of an agreement, treaty, or settlement.
-
B.
acquiredLandArea
Indicates the total area of land that has been obtained or taken possession of through an acquisition.
-
C.
grantedLandArea
Indicates that a specific area of land has been formally allocated or given by one party to another.
-
D.
hasCadastralArea
Indicates that an entity possesses or is associated with a specific cadastral (official land registry) area measurement.
-
E.
associatedLandRightsArea
Indicates the area of land for which specific land rights are linked or attributed to the referenced 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:11 p.m.