Triple
T10572009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace Community Church |
E249503
|
entity |
| Predicate | hasSpanishMinistry |
P40297
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Grace Community Church, hasSpanishMinistry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpanishMinistry Context triple: [Grace Community Church, hasSpanishMinistry, yes]
-
A.
hasMinister
Indicates that one entity serves as the minister (political, religious, or administrative official) responsible for or associated with another entity.
-
B.
hasMinistries
chosen
Indicates that an entity possesses, oversees, or is organized into one or more ministries as subordinate units or departments.
-
C.
hasMediaMinistry
Indicates that an entity operates, oversees, or is associated with a ministry or department responsible for media-related affairs.
-
D.
supportedMinistryOf
Indicates that one entity provided assistance, endorsement, or resources to help carry out the ministry or religious service activities of another entity.
-
E.
formedAsMinistry
Indicates that an organization or body was created or established in the form of a ministry.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52747a8d88190ab59333937180edc |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.