Triple
T9180621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claverack, New York |
E220316
|
entity |
| Predicate | languageOfEarlySettlers |
P82461
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [Claverack, New York, languageOfEarlySettlers, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfEarlySettlers Context triple: [Claverack, New York, languageOfEarlySettlers, Dutch]
-
A.
languageOfColonialSettlers
chosen
Indicates the language historically spoken by colonial settlers in a given place or context.
-
B.
languageOfFounders
Indicates the language or languages spoken or used by the founders of an entity.
-
C.
hasNotableEarlySettler
Indicates that an entity is associated with a historically significant person who was among its earliest settlers.
-
D.
languageOfAssimilation
Indicates the language used to integrate or absorb individuals or groups into a dominant culture or society.
-
E.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc251da448190a5c7f684dac15a84 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.