Triple
T28490932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dibley parish |
E720961
|
entity |
| Predicate | hasParishioner |
P4195
|
FINISHED |
| Object | Alice Tinker |
—
|
NE NERFINISHED |
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: Alice Tinker | Statement: [Dibley parish, hasParishioner, Alice Tinker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishioner Context triple: [Dibley parish, hasParishioner, Alice Tinker]
-
A.
hasParishionersFrom
Indicates that a religious institution or parish includes parishioners who come from a specified place or group.
-
B.
hasCongregation
Indicates that an entity is associated with or serves as the gathering place or organized group of worshippers for a religious community.
-
C.
hasParentChurch
Indicates that a church or religious organization is institutionally subordinate to or derived from another church, which serves as its parent or overseeing body.
-
D.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
E.
hasAdherent
chosen
Indicates that an entity is a follower, supporter, or member attached to another entity (such as a person, organization, belief, or movement).
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 3:01 a.m.