Triple
T896059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hope Baptist Church, Newark, New Jersey |
E19348
|
entity |
| Predicate | choirReputation |
P20808
|
FINISHED |
| Object | renowned |
—
|
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: renowned | Statement: [New Hope Baptist Church, Newark, New Jersey, choirReputation, renowned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choirReputation Context triple: [New Hope Baptist Church, Newark, New Jersey, choirReputation, renowned]
-
A.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
-
B.
reputationWithinLDP
Indicates that an entity holds a particular reputation or standing within a specified Local Development Plan (LDP) context.
-
C.
ecclesiasticalLevel
Indicates the hierarchical rank or status of an entity within an ecclesiastical (church) organization.
-
D.
ecclesiasticalRank
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
E.
churchOrder
Indicates the hierarchical or organizational structure that defines roles, authority, and governance within a church or religious institution.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad23d6e88190a2fb5e1e168a7b44 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.