Triple
T3643169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thracians |
E77235
|
entity |
| Predicate | culturalSuccessor |
P27713
|
FINISHED |
| Object | medieval Balkan populations |
—
|
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: medieval Balkan populations | Statement: [Thracians, culturalSuccessor, medieval Balkan populations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalSuccessor Context triple: [Thracians, culturalSuccessor, medieval Balkan populations]
-
A.
successorCulture
chosen
Indicates that one culture directly follows and continues or replaces another culture in time, inheriting or building upon its traditions or characteristics.
-
B.
successorCategory
Indicates that one category directly follows or replaces another in an ordered sequence or hierarchy.
-
C.
hasCulturalLegacyIn
Indicates that an entity has left a lasting cultural influence, impact, or heritage within a particular place, community, or cultural context.
-
D.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
E.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc35acf2c81908f60168e93b773b1 |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.