Triple
T31635929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NACCC |
E807312
|
entity |
| Predicate | memberChurchesType |
P45953
|
FINISHED |
| Object | autonomous Congregational churches |
—
|
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: autonomous Congregational churches | Statement: [NACCC, memberChurchesType, autonomous Congregational churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberChurchesType Context triple: [NACCC, memberChurchesType, autonomous Congregational churches]
-
A.
hasChurchType
chosen
Indicates that one entity (typically a church) is classified as being of a particular church type or category.
-
B.
hasMemberChurchesIn
Indicates that an organization or group includes member churches that are located within a specified geographic area or jurisdiction.
-
C.
hasMemberChurch
Indicates that a particular church is a constituent member of a larger religious organization, denomination, or church body.
-
D.
churchName
Indicates that one entity is the name or official designation of a church associated with another entity.
-
E.
memberChurchesFromCountries
Indicates that the member churches involved originate from or are associated with specific countries.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 30, 2026, 10:47 p.m.