Triple
T6585352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnin' |
E159205
|
entity |
| Predicate | featuresPoliticalThemes |
P31282
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Burnin', featuresPoliticalThemes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPoliticalThemes Context triple: [Burnin', featuresPoliticalThemes, true]
-
A.
politicalTheme
chosen
Indicates that something is related to, characterized by, or primarily concerned with politics, governance, or political issues.
-
B.
ideologicalTheme
Indicates that one entity embodies, expresses, or is centrally concerned with a particular ideology or set of ideological beliefs.
-
C.
mainPoliticalDevelopment
Indicates the primary or most significant political change, event, or evolution affecting an entity within a given period or context.
-
D.
currentPoliticalTrend
Indicates the prevailing direction or pattern of political attitudes, behaviors, or power dynamics at a given time.
-
E.
politicalIssueIn
Indicates that a political issue is relevant to, occurs within, or is associated with a particular geographic or political 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:54 p.m.