Triple
T19160865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tralles in Asia Minor |
E469048
|
entity |
| Predicate | wasBishopric |
P43325
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tralles in Asia Minor, wasBishopric, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBishopric Context triple: [Tralles in Asia Minor, wasBishopric, yes]
-
A.
hasBishopric
chosen
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
-
B.
wasPrinceBishopric
Indicates that an entity functioned as a prince-bishopric, combining both secular princely authority and ecclesiastical episcopal rule over a territory.
-
C.
bishopricEstablishedBefore
Indicates that the establishment of one bishopric occurred earlier in time than the establishment of another bishopric.
-
D.
dioceseBishop
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified diocese.
-
E.
hadPrinceBishop
Indicates that an entity was governed or overseen by a prince-bishop, combining secular and ecclesiastical authority.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebd093c81909a50f1119e284069 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.