Triple
T25311728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Gniezno |
E634621
|
entity |
| Predicate | establishedAsMetropolitanSee |
P66848
|
FINISHED |
| Object | 1000 |
—
|
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: 1000 | Statement: [Archdiocese of Gniezno, establishedAsMetropolitanSee, 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsMetropolitanSee Context triple: [Archdiocese of Gniezno, establishedAsMetropolitanSee, 1000]
-
A.
foundedAsMetropolis
chosen
Indicates that an entity was originally established or designated as a metropolis, typically a major or principal city.
-
B.
formerMetropolitanSee
Indicates that a location once served as the seat of a metropolitan bishop or archbishop but no longer holds that ecclesiastical status.
-
C.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
D.
hasMetropolitanRankOver
Indicates that one entity has a higher metropolitan rank or status than another entity.
-
E.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 1:27 p.m.