Triple
T30419948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Reformed Mission Church |
E773873
|
entity |
| Predicate | yearOfBelharAdoption |
P3399
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Dutch Reformed Mission Church, yearOfBelharAdoption, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfBelharAdoption Context triple: [Dutch Reformed Mission Church, yearOfBelharAdoption, 1982]
-
A.
yearOfOfficialDoctrine
Indicates the specific year in which an official doctrine, policy, or formal teaching was established or adopted.
-
B.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
C.
associatedSynodYear
Indicates the specific synod year with which an entity is associated or to which it pertains.
-
D.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
-
E.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 8:05 p.m.