Triple
T35050530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sackville, New Brunswick |
E1011316
|
entity |
| Predicate | laterSettledBy |
P183926
|
FINISHED |
| Object | British settlers |
—
|
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: British settlers | Statement: [Sackville, New Brunswick, laterSettledBy, British settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSettledBy Context triple: [Sackville, New Brunswick, laterSettledBy, British settlers]
-
A.
wasSettledBy
chosen
Indicates that a place or region came to be inhabited or established through the actions of a particular person, group, or population.
-
B.
legalStatusSettledBy
Indicates that the legal status of one entity is determined, resolved, or defined by another entity (such as a law, decision, or authority).
-
C.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
D.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
-
E.
settlementApprovedBy
Indicates that a proposed settlement has received formal approval or authorization from a specified person, group, or 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a004fd3caf48190b2ec063a7bf0756b |
completed | May 10, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a004f7672dc8190aca91d1ed855bf9a |
completed | May 10, 2026, 9:27 a.m. |
Created at: May 3, 2026, 4:01 p.m.