Triple
T28576798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Souls Unitarian Church (New York City) |
E723264
|
entity |
| Predicate | Forrest ChurchRole |
P96603
|
FINISHED |
| Object | longtime pastor |
—
|
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: longtime pastor | Statement: [All Souls Unitarian Church (New York City), Forrest ChurchRole, longtime pastor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Forrest ChurchRole Context triple: [All Souls Unitarian Church (New York City), Forrest ChurchRole, longtime pastor]
-
A.
seatOfChurchLeadership
Indicates the location that serves as the central administrative or authoritative base for a church’s leadership.
-
B.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
C.
typeOfHeadOfChurch
Indicates the specific role or office held by the person who serves as the head of a particular church or religious organization.
-
D.
clergymanTo
chosen
Indicates a relationship where one entity serves as or acts in the role of a clergyman in relation to another entity.
-
E.
evaluatedByChurch
Indicates that something has been assessed, judged, or reviewed by a church or church authority.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650c8f278819082855750b9b3d5ae |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:12 a.m.