Triple
T10752582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission for Building Fifty New Churches |
E253607
|
entity |
| Predicate | numberOfChurchesPartlyFunded |
P12144
|
FINISHED |
| Object | several additional 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: several additional churches | Statement: [Commission for Building Fifty New Churches, numberOfChurchesPartlyFunded, several additional churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfChurchesPartlyFunded Context triple: [Commission for Building Fifty New Churches, numberOfChurchesPartlyFunded, several additional churches]
-
A.
hasNumberOfChurches
chosen
Indicates the relationship that specifies how many churches are associated with a given entity.
-
B.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
C.
nonParticipatingChurch
Indicates that a church is not taking part in a specified activity, program, event, or agreement.
-
D.
numberOfParishes
Indicates the total count of parishes associated with a given entity.
-
E.
hasMemberChurchesIn
Indicates that an organization or group includes member churches that are located within a specified geographic area or jurisdiction.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dc184d0819085f8bc4edb034377 |
completed | April 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.