Triple
T26006521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Света Неделя |
E646773
|
entity |
| Predicate | имаСтатут |
P159658
|
FINISHED |
| Object | катедрален храм на Софийския митрополит |
—
|
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: катедрален храм на Софийския митрополит | Statement: [Света Неделя, имаСтатут, катедрален храм на Софийския митрополит]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имаСтатут Context triple: [Света Неделя, имаСтатут, катедрален храм на Софийския митрополит]
-
A.
isStatutory
Indicates that something exists, applies, or is defined by virtue of formal law or statute rather than by custom, contract, or other sources.
-
B.
statuteApprovedBy
Indicates that a statute has received formal approval or authorization from a specified person, body, or authority.
-
C.
hasMainStatute
Indicates that one legal document, case, or context is primarily governed, defined, or authorized by a specific statute.
-
D.
hasStatutes
Indicates that one entity possesses, is governed by, or is associated with a set of formal laws or statutes defined by another entity.
-
E.
statuteName
Indicates the specific legal statute or act by which something is formally designated, governed, or referenced.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057bd2708190bf400b153aca2f1b |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 9 a.m.