Triple
T18625169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pendle Deanery |
E455261
|
entity |
| Predicate | meetsThrough |
P32020
|
FINISHED |
| Object | Deanery Synod meetings |
—
|
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: Deanery Synod meetings | Statement: [Pendle Deanery, meetsThrough, Deanery Synod meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsThrough Context triple: [Pendle Deanery, meetsThrough, Deanery Synod meetings]
-
A.
meetsVia
chosen
Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
-
B.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
C.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
-
D.
meetsTo
Indicates that one entity comes together with another at a specific time and place for an encounter, appointment, or interaction.
-
E.
meetsBy
Indicates that one entity encounters or comes together with another entity, typically at a specific time or place.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f039b408190b51fe770a4c530ec |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.