Triple
T19024855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of England parish |
E465582
|
entity |
| Predicate | mayBeGroupedIn |
P35818
|
FINISHED |
| Object | benefice |
—
|
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: benefice | Statement: [Church of England parish, mayBeGroupedIn, benefice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeGroupedIn Context triple: [Church of England parish, mayBeGroupedIn, benefice]
-
A.
groupedInto
Indicates that multiple entities are collected or organized together as members of a common group or category.
-
B.
areSometimesGroupedWith
chosen
Indicates that two or more entities are occasionally but not consistently classified, treated, or considered together as part of the same group.
-
C.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
D.
isNarrativelyGroupedWith
Indicates that two or more elements are treated as part of the same narrative unit, sequence, or storyline within a larger context.
-
E.
containsGroup
Indicates that one entity includes or encompasses a specific group of entities within it.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6e271848190b67ad08af35b6796 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.