Triple
T26099782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Building Commission |
E658364
|
entity |
| Predicate | numberOfChurchesFunded |
P12144
|
FINISHED |
| Object | over 600 |
—
|
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: over 600 | Statement: [Church Building Commission, numberOfChurchesFunded, over 600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfChurchesFunded Context triple: [Church Building Commission, numberOfChurchesFunded, over 600]
-
A.
hasNumberOfChurches
chosen
Indicates the relationship that specifies how many churches are associated with a given entity.
-
B.
numberOfProjectsFunded
Indicates the quantity of projects that have received funding from a given source or entity.
-
C.
foundedChurchesIn
Indicates that an entity established or created one or more churches in a specified location or context.
-
D.
hasParishChurchesIn
Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
-
E.
onlyCompletedChurchBy
Indicates that the referenced entity is the sole church building project that was completed by the specified agent or entity.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 26, 2026, 7:54 p.m.