Triple
T22237592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blatchford |
E549631
|
entity |
| Predicate | firstResidentsArrived |
P140721
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Blatchford, firstResidentsArrived, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstResidentsArrived Context triple: [Blatchford, firstResidentsArrived, 2019]
-
A.
firstSettlersArrived
Indicates that the earliest group of settlers reached or came to a particular place or region.
-
B.
firstPermanentSettler
Indicates that the subject is the earliest individual or group to establish a lasting, continuous residence in the location or entity specified by the object.
-
C.
earlySettlers
chosen
Indicates that the associated entities were among the first people to inhabit or establish a community in a particular area.
-
D.
firstPermanentEuropeanSettlement
Indicates that the subject is the location of the earliest lasting European-established community in a given region or context.
-
E.
colonialPowerAtFirstArrival
Indicates that a specified colonial power was the first to arrive and establish a presence or control in a given territory or region.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f13210eb9c8190bc40d06c393e0d9a |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.