Triple
T28381472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Mellon of Rouen |
E718900
|
entity |
| Predicate | hasPlaceOfBishopric |
P179795
|
FINISHED |
| Object | Rouen |
—
|
NE NERFINISHED |
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: Rouen | Statement: [Saint Mellon of Rouen, hasPlaceOfBishopric, Rouen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceOfBishopric Context triple: [Saint Mellon of Rouen, hasPlaceOfBishopric, Rouen]
-
A.
hasBishopric
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
-
B.
countryOfBishopric
Indicates the country in which a given bishopric (episcopal see or diocese) is located or to which it belongs.
-
C.
bishopricEstablishedBefore
Indicates that the establishment of one bishopric occurred earlier in time than the establishment of another bishopric.
-
D.
hadPrinceBishop
Indicates that an entity was governed or overseen by a prince-bishop, combining secular and ecclesiastical authority.
-
E.
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.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: April 28, 2026, 1:06 a.m.