Triple
T1392907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baloch people |
E30599
|
entity |
| Predicate | culturalExpression |
P11746
|
FINISHED |
| Object | Balochi poetry |
—
|
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: Balochi poetry | Statement: [Baloch people, culturalExpression, Balochi poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalExpression Context triple: [Baloch people, culturalExpression, Balochi poetry]
-
A.
hasCulturalExpression
chosen
Indicates that an entity embodies, manifests, or is associated with a particular cultural form, practice, or expression.
-
B.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
C.
culturalSphere
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
D.
culturalMovement
Indicates that an entity is associated with, participates in, or belongs to a particular cultural movement or trend.
-
E.
culturalExport
Indicates that something originating in one culture is transmitted, adopted, or influential in another culture or region.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c360a7f08190ab7e903764b06fdf |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.