Triple
T7099249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Central New York |
E165410
|
entity |
| Predicate | canBeAssistedBy |
P2463
|
FINISHED |
| Object | suffragan bishops |
—
|
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: suffragan bishops | Statement: [Bishop of Central New York, canBeAssistedBy, suffragan bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAssistedBy Context triple: [Bishop of Central New York, canBeAssistedBy, suffragan bishops]
-
A.
requiresAssistanceFrom
Indicates that one entity depends on help, support, or intervention from another entity to perform an action or fulfill a need.
-
B.
wasAssistedBy
Indicates that an entity carried out an action or achieved a result with the help or support of another entity.
-
C.
canBe
chosen
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
E.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e58531c88190a32746f9a97da709 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.