Triple
T23915424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baptist conventions |
E602069
|
entity |
| Predicate | mayAffiliateWith |
P111930
|
FINISHED |
| Object | larger Baptist world bodies |
—
|
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: larger Baptist world bodies | Statement: [Baptist conventions, mayAffiliateWith, larger Baptist world bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAffiliateWith Context triple: [Baptist conventions, mayAffiliateWith, larger Baptist world bodies]
-
A.
allowsAffiliationOf
chosen
Indicates that one entity grants permission or enables another entity to establish or hold an affiliation with it.
-
B.
hasAffiliate
Indicates that one entity is formally associated with another as an affiliate, typically through a partnership, membership, or subordinate organizational relationship.
-
C.
hasAffiliatesIn
Indicates that an entity maintains affiliated entities, branches, or partners located within a specified place or region.
-
D.
mayContractWith
Indicates that one entity is permitted or authorized to enter into a contractual agreement with another entity.
-
E.
mayHost
Indicates that an entity is permitted or able to serve as the location or organizer for another entity or event.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce9917808190ad66a4e276a24b3d |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:40 p.m.