Triple
T23022525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Laity of the Church of England |
E573205
|
entity |
| Predicate | numberOfConstituentHousesInSynod |
P150710
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [House of Laity of the Church of England, numberOfConstituentHousesInSynod, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfConstituentHousesInSynod Context triple: [House of Laity of the Church of England, numberOfConstituentHousesInSynod, 3]
-
A.
numberOfSynods
Indicates the count of synods associated with or held by a given entity.
-
B.
hasSynodMembers
Indicates that a synod includes or is composed of the specified members.
-
C.
hasSynod
Indicates that an entity is associated with, governed by, or participates in a particular synod (a formal ecclesiastical council or assembly).
-
D.
typeOfSynod
Indicates the specific kind or category to which a particular synod belongs.
-
E.
hasSynodicalGovernment
Indicates that an entity is governed or administered through a synodical (council-based, typically ecclesiastical) system of decision-making.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183ea23088190b2f42d9bf01514ac |
completed | April 29, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:52 p.m.