Triple
T38663212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambeth Articles 1595 |
E940385
|
entity |
| Predicate | associatedCleric |
P192508
|
FINISHED |
| Object | Richard Fletcher |
E585856
|
NE 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: Richard Fletcher | Statement: [Lambeth Articles 1595, associatedCleric, Richard Fletcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCleric Context triple: [Lambeth Articles 1595, associatedCleric, Richard Fletcher]
-
A.
hasClericalAssociation
chosen
Indicates a relationship in which an entity is connected to or involved with clerical roles, duties, or religious office.
-
B.
associatedWithSacrament
Indicates a relationship where something is connected or related to a specific sacrament in a religious or ritual context.
-
C.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
-
D.
associatedWithApostle
Indicates a relationship in which an entity is connected or linked in some notable way to an apostle.
-
E.
associatedCult
Indicates that an entity is connected or linked to a particular cult, typically through membership, affiliation, or influence.
- F. None of above.
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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd6785c08190b2f7c93735c31c3c |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.