Triple
T407417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Paris (1763) |
E9412
|
entity |
| Predicate | transferredTerritoryFrom |
P6398
|
FINISHED |
| Object | Canada from France |
—
|
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: Canada from France | Statement: [Treaty of Paris (1763), transferredTerritoryFrom, Canada from France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredTerritoryFrom Context triple: [Treaty of Paris (1763), transferredTerritoryFrom, Canada from France]
-
A.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
-
B.
transmittedFrom
Indicates that something (such as information, a signal, or a disease) has been passed or conveyed from one source entity to another.
-
C.
removedFromJurisdictionOf
chosen
Indicates that authority, control, or legal oversight over an entity has been taken away from a particular jurisdiction.
-
D.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
conqueredFrom
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbd766c8190bb8a91605929156a |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.