Triple
T34253139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hlebine School |
E878800
|
entity |
| Predicate | notableWorkThemes |
P201579
|
FINISHED |
| Object | village life |
—
|
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: village life | Statement: [Hlebine School, notableWorkThemes, village life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkThemes Context triple: [Hlebine School, notableWorkThemes, village life]
-
A.
notableTheme
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
B.
notableWorkSubject
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
C.
hasNotableWorkTheme
chosen
Indicates that there is a notable work whose central theme or subject matter is characterized by the related concept.
-
D.
notableWorkAspect
Indicates a specific characteristic, feature, or component that is a significant or defining part of a notable work.
-
E.
notableWorkAboutSubject
Indicates that a notable work (such as a book, film, or artwork) is about, focuses on, or significantly concerns the given subject.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.