Triple
T30419943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Reformed Mission Church |
E773873
|
entity |
| Predicate | racialStructure |
P169198
|
FINISHED |
| Object | racially segregated church |
—
|
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: racially segregated church | Statement: [Dutch Reformed Mission Church, racialStructure, racially segregated church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racialStructure Context triple: [Dutch Reformed Mission Church, racialStructure, racially segregated church]
-
A.
racialComposition
Indicates the proportional makeup of different racial groups within a given population or entity.
-
B.
raceGroup
Indicates that the subject belongs to, or is categorized within, a particular racial or ethnic group.
-
C.
raceRole
Indicates the specific role, position, or function an entity holds within a race or racing event.
-
D.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
E.
ethnicComponents
Indicates that an entity is composed of, associated with, or characterized by one or more specified ethnic groups or ethnic origins.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6864cd7548190b3e12ef2fe253ad8 |
completed | May 2, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:05 p.m.