Triple
T10543240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of Saint John XXIII of Sofia |
E248747
|
entity |
| Predicate | metropolitanStatus |
P24765
|
FINISHED |
| Object | exempt |
—
|
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: exempt | Statement: [Eparchy of Saint John XXIII of Sofia, metropolitanStatus, exempt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metropolitanStatus Context triple: [Eparchy of Saint John XXIII of Sofia, metropolitanStatus, exempt]
-
A.
metropolitanStatusHeld
chosen
Indicates that an entity holds or is assigned a particular metropolitan status (e.g., being designated as part of a metropolitan area or category).
-
B.
metropolitan
Indicates that a location is part of, belongs to, or lies within a specified metropolitan (urban) area.
-
C.
isMetropolitanFor
Indicates that one entity serves as the primary metropolitan center or urban hub for another entity (such as a region, area, or service).
-
D.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
-
E.
metropolitanOf
Indicates that one place serves as the primary metropolitan center or core urban area for another place or region.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d51911b10481909e6e548879e8de36 |
completed | April 7, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:32 p.m.