Triple
T28557712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Amsterdam |
E723050
|
entity |
| Predicate | denominationOfChurchWithin |
P61129
|
FINISHED |
| Object | Protestant |
—
|
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: Protestant | Statement: [Fort Amsterdam, denominationOfChurchWithin, Protestant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationOfChurchWithin Context triple: [Fort Amsterdam, denominationOfChurchWithin, Protestant]
-
A.
denominationOfChurchAbove
Indicates that one church is of a higher or superior denomination level or rank relative to another church.
-
B.
denominationOfMainChurch
chosen
Indicates the religious denomination to which the main church of an entity belongs.
-
C.
denominations
Indicates the specific units or categories into which something (often money, values, or items) is divided or classified.
-
D.
principalChurchOf
Indicates that one church serves as the main or most important church associated with a particular entity, such as a region, denomination, or institution.
-
E.
denominationalHost
Indicates that one entity serves as the hosting or organizing body for a religious denomination-related event, activity, or function involving another entity.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 3:46 a.m.