Triple
T25398521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redeemer Presbyterian Church |
E636356
|
entity |
| Predicate | multiSite |
P21554
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Redeemer Presbyterian Church, multiSite, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiSite Context triple: [Redeemer Presbyterian Church, multiSite, true]
-
A.
supportsMultisite
chosen
Indicates that an entity is capable of operating across or managing multiple sites or locations within a single setup.
-
B.
modernSiteCorrespondsTo
Indicates that a present-day site occupies, aligns with, or directly relates to the location or extent of another (typically historical or earlier) site.
-
C.
isSatelliteSiteOf
Indicates that one site functions as a subsidiary, dependent, or secondary location associated with another primary or main site.
-
D.
numberOfSites
Indicates the total count of distinct sites associated with or involved in the given entity or context.
-
E.
supportsMultisiteViaExtensions
Indicates that the subject provides multisite functionality through the use of additional extensions or plugins rather than built-in support.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f728fc8190982b260fa700002c |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:50 p.m.