Triple
T5386868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgars |
E120221
|
entity |
| Predicate | ethnogenesisContribution |
P51841
|
FINISHED |
| Object | formation of the Bulgarian people |
—
|
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: formation of the Bulgarian people | Statement: [Bulgars, ethnogenesisContribution, formation of the Bulgarian people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnogenesisContribution Context triple: [Bulgars, ethnogenesisContribution, formation of the Bulgarian people]
-
A.
ethnogenesisOf
chosen
Indicates the process or relationship by which a particular group, culture, or people comes into existence or forms its distinct identity.
-
B.
ethnogenesisInCentury
Indicates the century during which a particular ethnic group or people came into existence or was formed.
-
C.
ethnogenesisRegion
Indicates the geographic region where the formation or emergence of an ethnic group took place.
-
D.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
-
E.
ethnolinguisticGroups
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f6f39c8190aa6af12370e3d12b |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.