Triple
T17189829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinderhook Reformed Church |
E417197
|
entity |
| Predicate | languageOfEarlyServices |
P126669
|
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: [Kinderhook Reformed Church, languageOfEarlyServices, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfEarlyServices Context triple: [Kinderhook Reformed Church, languageOfEarlyServices, Dutch]
-
A.
currentLanguageOfServices
Indicates that a specified language is the one presently used to provide or deliver certain services.
-
B.
languageOfEarlyDevelopment
Indicates that a specified language is used during the initial or formative stages of an entity’s development.
-
C.
languageOfEarliestForm
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
-
D.
serviceBranchLanguage
Indicates the language or languages used or officially recognized by a particular branch of a service (such as a military or organizational branch).
-
E.
serviceBrandLanguage
Indicates the language or languages in which a service brand communicates or is presented.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d986b60819085c515101cfe65fe |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:37 a.m.