Triple
T23915434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baptist conventions |
E602069
|
entity |
| Predicate | oftenAdopt |
P73186
|
FINISHED |
| Object | constitutions and bylaws |
—
|
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: constitutions and bylaws | Statement: [Baptist conventions, oftenAdopt, constitutions and bylaws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenAdopt Context triple: [Baptist conventions, oftenAdopt, constitutions and bylaws]
-
A.
adopts
Indicates that one entity formally takes another into its care, control, or use, assuming ongoing responsibility or ownership.
-
B.
adoptionFrequency
chosen
Indicates how often an entity adopts or takes on another entity, such as a practice, item, or individual, over a given period.
-
C.
canAdopt
Indicates that one entity has the ability or permission to adopt another entity.
-
D.
adoption
Indicates the legal or formal act by which one party assumes parental or custodial responsibility for another, typically a child, creating a recognized parent–child relationship.
-
E.
adoptionOccasion
Indicates the event or circumstance under which an adoption takes place or is formally recognized.
- 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.