Triple
T10935357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reverend Mr. Hooper |
E258317
|
entity |
| Predicate | relationshipToCongregation |
P26859
|
FINISHED |
| Object | 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: pastor | Statement: [Reverend Mr. Hooper, relationshipToCongregation, pastor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCongregation Context triple: [Reverend Mr. Hooper, relationshipToCongregation, pastor]
-
A.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
B.
hasCongregation
chosen
Indicates that an entity is associated with or serves as the gathering place or organized group of worshippers for a religious community.
-
C.
hasParentChurch
Indicates that a church or religious organization is institutionally subordinate to or derived from another church, which serves as its parent or overseeing body.
-
D.
relationshipToEvent
Indicates the specific way an entity is connected or related to a particular event.
-
E.
relationToCouncil
Indicates the nature or type of connection an entity has with a council, such as membership, oversight, affiliation, or governance relationship.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770aee178819082c1671a37ff7d82 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.