Triple
T26006520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Света Неделя |
E646773
|
entity |
| Predicate | разпознаваемост |
P99189
|
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.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
-
B.
recognizedFeature
Indicates that a particular feature has been identified and acknowledged as present or valid in relation to an entity or context.
-
C.
recognizableFor
chosen
Indicates that one entity is known or identifiable because of a particular characteristic, feature, or association with another entity.
-
D.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
-
E.
primaryRecognition
Indicates that one entity is the main or foremost source of acknowledgment, credit, or validation for another entity.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 9 a.m.