Triple
T34437245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silas |
E883995
|
entity |
| Predicate | helpedFoundChurch |
P178941
|
FINISHED |
| Object | church in Philippi |
—
|
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: church in Philippi | Statement: [Silas, helpedFoundChurch, church in Philippi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedFoundChurch Context triple: [Silas, helpedFoundChurch, church in Philippi]
-
A.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
B.
locatesChurchWithin
Indicates that one entity places or establishes a church within the boundaries or interior of another entity.
-
C.
churchName
Indicates that one entity is the name or official designation of a church associated with another entity.
-
D.
churchServed
Indicates that one entity has provided religious service, ministry, or leadership within the other entity’s church or congregation.
-
E.
viewsOtherChurchesAs
Indicates that one entity regards or perceives other churches in a particular way or from a specific evaluative perspective.
- F. None of above. chosen
Provenance (4 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.