Triple
T25714377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocodilopolis |
E644819
|
entity |
| Predicate | laterChristianBishopric |
P173670
|
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: [Crocodilopolis, laterChristianBishopric, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterChristianBishopric Context triple: [Crocodilopolis, laterChristianBishopric, yes]
-
A.
modernSuccessorDiocese
Indicates that one diocese is the present-day or contemporary successor to an earlier, historically related diocese.
-
B.
dioceseLater
Indicates that one diocese exists or is established later in time than another diocese.
-
C.
wasPrinceBishopric
Indicates that an entity functioned as a prince-bishopric, combining both secular princely authority and ecclesiastical episcopal rule over a territory.
-
D.
establishedAsAreaBishopricIn
Indicates that an ecclesiastical jurisdiction or region was formally constituted or designated as an area bishopric in a specified year or at a specified time.
-
E.
wasPrinceBishopricUntil
Indicates that an entity functioned as a prince-bishopric up to (and including, or until) a specified point in time.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 21, 2026, 9:37 p.m.