Triple
T4698758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letters |
E104213
|
entity |
| Predicate | containsCorrespondenceWith |
P58603
|
FINISHED |
| Object | church leaders |
—
|
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: church leaders | Statement: [Letters, containsCorrespondenceWith, church leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCorrespondenceWith Context triple: [Letters, containsCorrespondenceWith, church leaders]
-
A.
partiallyCorrespondsTo
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
-
B.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
C.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
D.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
E.
hasCorrelativesSystem
Indicates that one entity possesses or employs a system of correlatives—structured, corresponding elements or forms that are systematically related to each other.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:17 p.m.