Triple
T6785334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal polity |
E155786
|
entity |
| Predicate | placesAuthorityIn |
P9895
|
FINISHED |
| Object | individual 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: individual bishops | Statement: [Episcopal polity, placesAuthorityIn, individual bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placesAuthorityIn Context triple: [Episcopal polity, placesAuthorityIn, individual bishops]
-
A.
areaOfAuthority
Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
-
B.
decisionPlace
Indicates the location where a decision is made or formally determined.
-
C.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
designatesAuthority
chosen
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
E.
roleAsPlace
Indicates that an entity functions or is used as a place or location in relation to another entity or event.
- 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.