Triple
T2443745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronck family |
E53337
|
entity |
| Predicate | settlerType |
P38521
|
FINISHED |
| Object | European colonists |
—
|
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: European colonists | Statement: [Bronck family, settlerType, European colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settlerType Context triple: [Bronck family, settlerType, European colonists]
-
A.
humanSettlementType
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
B.
numberOfOriginalSettlerFamilies
Indicates the count of distinct families that were part of the initial group of settlers in a given place or community.
-
C.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
D.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
E.
sisterSettlement
Indicates that two settlements are formally paired or twinned, typically to promote cultural, social, or economic exchange.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
| PDg | Predicate description generation | batch_69abcabe646c8190855d13b5dff07b97 |
completed | March 7, 2026, 6:50 a.m. |
Created at: March 6, 2026, 9:43 p.m.