Triple
T30419949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Reformed Mission Church |
E773873
|
entity |
| Predicate | placeOfBelharAdoption |
P4186
|
FINISHED |
| Object | Belhar, Cape Town |
—
|
NE NERFINISHED |
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: Belhar, Cape Town | Statement: [Dutch Reformed Mission Church, placeOfBelharAdoption, Belhar, Cape Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfBelharAdoption Context triple: [Dutch Reformed Mission Church, placeOfBelharAdoption, Belhar, Cape Town]
-
A.
placeOfFormalAdoption
Indicates the location where a formal adoption legally took place.
-
B.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
C.
adoptedInCity
chosen
Indicates that an adoption event took place within a specific city.
-
D.
adoptionCountry
Indicates the country in which the adoption of an entity (such as a person, animal, or item) legally took place.
-
E.
saidToHaveBeenAdoptedBy
Indicates that one entity is reported or believed to have been adopted by another entity, without asserting it as an established fact.
- 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 8:05 p.m.