Triple
T6785343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal polity |
E155786
|
entity |
| Predicate | distinguishesRoleOf |
P5687
|
FINISHED |
| Object | bishop from presbyter or priest |
—
|
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: bishop from presbyter or priest | Statement: [Episcopal polity, distinguishesRoleOf, bishop from presbyter or priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinguishesRoleOf Context triple: [Episcopal polity, distinguishesRoleOf, bishop from presbyter or priest]
-
A.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
B.
comparativeRole
Indicates a relationship where one entity’s role is compared to another’s in terms of level, importance, or function.
-
C.
acknowledgesRoleOf
Indicates that one entity explicitly recognizes and accepts the position, function, or authority that another entity holds.
-
D.
identificationRole
chosen
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
-
E.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28de0348190998751fd546bfd02 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.